HomeSort by relevance Sort by last modified time
    Searched refs:should (Results 1 - 25 of 109) sorted by null

1 2 3 4 5

  /test/ohacts/src/tset/dataservice/doc/assertions/
dataservice 32 1. Registration of Resource types for the data service should be successful.
34 2. Creation of resource group(s) and resources should be successful.
36 3. Bringing the resource group(s) online should be successful.
38 4. Disabling Application resources should be successful.
40 5. Enabling Application resources should be successful.
42 6. Bringing the resource group(s) offline should be successful.
45 should be successful.
48 should be successful.
51 should be successful.
54 Retry_count within the Retry_interval should result in restartin
    [all...]
dataservice_reboot 32 1. Rebooting the primary node should not affect the availability
35 2. Killing rgmd on primary node should not affect the availability
38 3. Failback property of the resource group should work as expected.
42 5. After the node is rebooted all the resource groups should come online.
  /test/ohacts/src/doc/dataservice/
testcases 33 1. Registration of Resource types for the data service should be successful.
35 2. Creation of resource group(s) and resources should be successful.
37 3. Bringing the resource group(s) online should be successful.
39 4. Disabling Application resources should be successful.
41 5. Enabling Application resources should be successful.
44 offline should be successful.
47 should be successful.
50 should be successful.
53 should be successful.
56 Retry_count within the Retry_interval should result in restartin
    [all...]
  /test/ohacts/src/tset/sanity/doc/assertions/
transport_reboot 43 If cluster node was rebooted the connection to that node should
45 node should be rejected in one to three seconds.
53 3. The connection should be reset in one to three seconds.
55 request should be rejected in one to three seconds.
transport 43 Downing the primary interface should not affect communication
64 Downing the secondary interface should not affect communication
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/utils/
README 29 This directory should contain the source (and binaries) of any
  /test/ohacts/src/doc/dataservice/non_reboot/
test_14.txt 33 Removing application resource should be successful.
44 and resource groups should continue to be registered.
test_4.txt 33 Disabling Application resources should be successful.
47 and resource groups should continue to be online.
54 Client program should fail.
test_5.txt 33 Enabling Application resources should be successful.
47 and resource groups should continue to be online.
54 Client program should pass.
test_15.txt 33 Removing the resource group should be successful.
test_10.txt 34 Retry_count within the Retry_interval should result in restarting
50 (It should be automatically restarted)
test_7.txt 33 Disabling the fault monitor for the application resources should be
48 and resource groups should continue to be online.
test_8.txt 33 Enabling the fault monitor for the application resources should be
48 and resource groups should continue to be online.
test_11.txt 34 killed, they should automatically be restarted.
55 (It should be automatically restarted)
test_12.txt 33 Killing pnmd process should not affect the data service.
51 (It should be automatically restarted)
test_18.txt 33 If a daemon process associated with a resource is killed, it should
55 (It should be automatically restarted)
test_2.txt 33 Creation of resource group(s) and resources should be successful.
  /test/stcnv/usr/src/suites/nfs/nfsgen/tests/acl/
README 34 The exported filesystem on server side should be ZFS.
36 should set SHRDIR variable to a directory based on ZFS.
39 When SETUP is set to none, the user should create the
52 In addition, the exported filesystem on the server should
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/utils/
README 30 This directory should contain the source (and binaries) of any
  /test/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/delete_port/
ASSERTIONS 34 should be in the list returned by FCOE_GetPortList(); If it is
35 deleted by FCOE_DeletePort(), it should not be in the list
61 it should return an expected value if the parameter mac
84 it should return an expected value if the parameter mac
  /test/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/get_port_list/
ASSERTIONS 33 they should be in the list returned by FCOE_GetPortList();
55 the port number returned by FCOE_GetPortList() should be zero;
76 DESCRIPTION: There should be a failure if NULL is passed as first parameter
98 DESCRIPTION: There should be a failure if NULL is passed as second parameter
  /test/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/create_port/
ASSERTIONS 34 should be in the list returned by FCOE_GetPortList().
56 should return an expected value if the first parameter
78 should return an expected value if the first parameter
101 by FCOE_CreatePort(), it should be in the list returned by
124 PWWN and NWWN by FCOE_CreatePort(), it should return a
146 should return an expected value if the second parameter
169 should return an successful value if the last parameter
  /test/ontest-stc2/src/suites/net/nicdrv/doc/
nicdrv.assert 41 - For each file size, the ftp traffic should be sustained for at least 900 sec.
42 - All FTP sessions should pass without any errors
70 - All TCP/UDP sessions should pass without any errors
95 - Ping should pass with zero packet loss
122 - Test should pass without data corruptions
178 - All operations should pass without any errors.
179 - Driver link/speed status should be recovered to original status.
210 - All operations should pass without any errors.
211 - Driver link/speed status should be recovered to original status.
267 - All of tests should pass without any error
    [all...]
  /test/ontest-stc2/src/suites/os/smf/tests/svcadm/doc/
ASSERTIONS 33 instance that is in the disabled state should fail with exit 1.
55 instance that is in the disabled state should fail with exit 1.
81 svcadm force degraded <invalid-fmri> should fail with exit 1
82 svcadm force degraded <invalid name> should fail with exit 1
83 svcadm -v force degraded <invalid-fmri> should fail with exit 1
84 svcadm -v force degraded <invalid-name> should fail with exit 1
90 should fail with exit 1.
107 svcadm force degraded <without any arguments> should fail with
109 svcadm -v force degraded <without any arguments> should fail with
127 has multiple instances should fail and exit 1
    [all...]
  /test/stcnv/usr/src/suites/os/smf/tests/svcadm/doc/
ASSERTIONS 33 instance that is in the disabled state should fail with exit 1.
55 instance that is in the disabled state should fail with exit 1.
81 svcadm force degraded <invalid-fmri> should fail with exit 1
82 svcadm force degraded <invalid name> should fail with exit 1
83 svcadm -v force degraded <invalid-fmri> should fail with exit 1
84 svcadm -v force degraded <invalid-name> should fail with exit 1
90 should fail with exit 1.
107 svcadm force degraded <without any arguments> should fail with
109 svcadm -v force degraded <without any arguments> should fail with
127 has multiple instances should fail and exit 1
    [all...]

Completed in 5100 milliseconds

1 2 3 4 5