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

1 2 3 4 5 6 7 8 91011>>

  /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.
59 killed, they should automatically be restarted
    [all...]
  /test/ohacts/src/tset/sanity/doc/assertions/
transport_reboot 44 be reset in one to three seconds and new connect request to that
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.
  /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.
61 killed, they should automatically be restarted
    [all...]
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/utils/
README 30 tools to be used for any nfsv4/tests to test NFSv4 functions,
  /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.
49 3. Get the nodelist where this resource group can be mastered and
test_5.txt 33 Enabling Application resources should be successful.
47 and resource groups should continue to be online.
49 3. Get the nodelist where this resource group can be mastered and
test_7.txt 33 Disabling the fault monitor for the application resources should be
48 and resource groups should continue to be online.
50 3. Get the nodelist where this resource group can be mastered and
test_8.txt 33 Enabling the fault monitor for the application resources should be
48 and resource groups should continue to be online.
50 3. Get the nodelist where this resource group can be mastered and
test_15.txt 33 Removing the resource group should be successful.
  /test/ohacts/src/tset/geo/doc/assertions/
geo_avs_mult_pgs 48 Activate PGs. (AVS will be sync to REP state.)
51 <cluster-2> will be the primary cluster.
54 <cluster-1> will be the primary cluster.
69 Activate PGs. (AVS will be sync to REP state.)
73 <cluster-2> will be the primary cluster. This should fail.
75 <cluster-2> will be the primary cluster. This should pass.
78 <cluster-1> will be the primary cluster.
95 Activate PG. (AVS will be sync to REP state.)
97 <cluster-2> will be the primary cluster.
116 Activate PGs. (AVS will be sync to REP state.
    [all...]
geo_avs_reboot 47 'geopg switchover' back, so that pg will be primary-ed on
53 = Activate PG. (AVS will be sync to REP state.)
56 = Issue 'geopg takeover' on pg so that it will be primary-ed
61 <cluster-1> will be the primary cluster.
74 will be primary-ed on original primary cluster.
79 = Activate PG. (AVS will be sync to REP state.)
81 = Issue 'geopg takeover' on pg so that it will be primary-ed on
87 <cluster-1> will be the primary cluster.
101 = Activate PG. (AVS will be sync to REP state.)
119 = Activate PG. (AVS will be sync to REP state.
    [all...]
geo_avs_mult_pgs_reboot 48 that pgs will be primary-ed on original primary cluster.
53 = Activate PGs. (AVS will be sync to REP state.)
55 = Issue 'geopg takeover' on pgs so that they will be primary-ed on
61 <cluster-1> will be the primary cluster.
  /test/ontest-stc2/src/tools/stf/bin/
mstf_addassert.ksh 35 The -t argument must be provided first.
37 Unline stf_addassert, -c takes a single argument, so the command to be
38 invoked must be quoted. However, the -c option may be present
39 multiple times, and all specified commands will be executed
109 print -u2 "At least one command must be specified via -c"
  /test/stcnv/usr/src/tools/stf/bin/
mstf_addassert.ksh 35 The -t argument must be provided first.
37 Unline stf_addassert, -c takes a single argument, so the command to be
38 invoked must be quoted. However, the -c option may be present
39 multiple times, and all specified commands will be executed
109 print -u2 "At least one command must be specified via -c"
  /test/ontest-stc2/src/tools/stf/contrib/smf/
README.libsmf 30 way to interact with SMF, the following will be added to the contributed
34 presence of SMF will be added to src/tools/stf/contrib/smf. The commands
35 will be invocable equivalents to the functions in the library. So a test
40 and installed files. All source files will be in src/tools/stf/contrib/smf (a
41 new directory). When installed, the library may be loaded from
43 be in ${STF_TOOLS}/contrib/smf/bin. Since STC 2.0 adds the bin directory to
44 the PATH, all of the commands may be invoked sans any path. e.g.
71 # Will return 0 if smf appears to be installed and should be
82 # the FMRI named to have the status passed. The command may be
    [all...]
  /test/stcnv/usr/src/tools/stf/contrib/smf/
README.libsmf 30 way to interact with SMF, the following will be added to the contributed
34 presence of SMF will be added to src/tools/stf/contrib/smf. The commands
35 will be invocable equivalents to the functions in the library. So a test
40 and installed files. All source files will be in src/tools/stf/contrib/smf (a
41 new directory). When installed, the library may be loaded from
43 be in ${STF_TOOLS}/contrib/smf/bin. Since STC 2.0 adds the bin directory to
44 the PATH, all of the commands may be invoked sans any path. e.g.
71 # Will return 0 if smf appears to be installed and should be
82 # the FMRI named to have the status passed. The command may be
    [all...]
  /test/stcnv/usr/src/tools/genutils/smf/
README.libsmf 30 way to interact with SMF, the following will be added to the STC
34 presence of SMF will be added to usr/src/tools/genutils/smf. The commands
35 will be invocable equivalents to the functions in the library. So a test
40 and installed files. All source files will be in usr/src/tools/genutils/smf (a
41 new directory). When installed, the library may be loaded from
42 $STC_GENUTILS/include/libsmf.shlib, and the invocable commands will be in
45 all of the commands may be invoked sans any path. e.g.
72 # Will return 0 if smf appears to be installed and should be
83 # the FMRI named to have the status passed. The command may be
    [all...]
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/instance/scf_instance_create/
ASSERTIONS 51 No separate test will be written. This assertion will be
71 No separate test will be written for this assertion.
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/service/scf_service_create/
ASSERTIONS 50 No separate test will be written for this assertion.
62 No separate test will be written for this assertion.
75 To be implemented when support for non-local repositories is available.
  /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/instance/scf_instance_create/
ASSERTIONS 51 No separate test will be written. This assertion will be
71 No separate test will be written for this assertion.
  /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/service/scf_service_create/
ASSERTIONS 50 No separate test will be written for this assertion.
62 No separate test will be written for this assertion.
75 To be implemented when support for non-local repositories is available.
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/server/
README 38 must be found in the same directory as the script. In
43 Consists of the types of test files/directories to be
48 This is intentionally separate to allow server files to be
51 be executed if NFS traffic is allowed between the client
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-mid/property/scf_simple_prop_next_opaque/
ASSERTIONS 42 need to be implemented
57 need to be implemented
72 need to be implemented
87 need to be implemented
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-mid/property/scf_simple_prop_next_ustring/
ASSERTIONS 42 need to be implemented
57 need to be implemented
72 need to be implemented
87 need to be implemented

Completed in 5710 milliseconds

1 2 3 4 5 6 7 8 91011>>