| /test/ontest-stc2/src/suites/security/kmf/tests/kmfcfg/ |
| kmfcfg_create_001.ksh | 40 # will return error without trust anchor attributes.
42 # ta-name="Subject DN" " will return error.
44 # ta-serial=serialNumber" will return error.
46 # ignore-trust-anchor=true" will return success.
48 # ta-name="Subject DN" ta-serial=serialNumber" will
73 will return error without trust anchor attributes.
75 ta-name="Subject DN"" will return error.
77 ta-serial=serialNumber " will return error.
79 ignore-trust-anchor=true " will return success.
82 will return success
[all...] |
| /test/stcnv/usr/src/suites/security/kmf/tests/kmfcfg/ |
| kmfcfg_create_001.ksh | 40 # will return error without trust anchor attributes.
42 # ta-name="Subject DN" " will return error.
44 # ta-serial=serialNumber" will return error.
46 # ignore-trust-anchor=true" will return success.
48 # ta-name="Subject DN" ta-serial=serialNumber" will
73 will return error without trust anchor attributes.
75 ta-name="Subject DN"" will return error.
77 ta-serial=serialNumber " will return error.
79 ignore-trust-anchor=true " will return success.
82 will return success
[all...] |
| /test/stcnv/usr/src/suites/nfs/nfsgen/tests/recovery/ |
| README | 32 tests will NOT run and return UNSUPPORTED.
34 Some tests in recovery will test conflicting lock, original scenario is
|
| /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.
90 the PG will succeed.
95 Activate PG. (AVS will be sync to REP state.)
97 <cluster-2> will be the primary cluster
[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.
|
| geo_avs_rbac | 52 Activate PG. (AVS will be sync to REP state.)
55 <cluster-2> will be the primary cluster.
58 <cluster-1> will be the primary cluster.
75 Activate PG. (AVS will be sync to REP state.)
78 <cluster-2> will be the primary cluster.
81 <cluster-1> will be the primary cluster.
95 Activate PG. (AVS will be sync to REP state.)
103 that PG will be primary-ed on original primary cluster.
121 Activate PG. (AVS will be sync to REP state.)
123 <cluster-2> will be the primary cluster
[all...] |
| geo_avs | 48 = Activate PG. (AVS will be sync to REP state.)
50 <cluster-2> will be the primary cluster.
53 <cluster-1> will be the primary cluster.
70 = Activate PG. (AVS will be sync to REP state.)
77 = Issue 'geopg switchover' from <cluster-1> so that <cluster-2> will
81 = Issue 'geopg switchover' so that <cluster-2> will be the primary
91 the PG will succeed.
96 = Activate PG. (AVS will be sync to REP state.)
98 <cluster-2> will be the primary cluster.
120 = Activate PG. (AVS will be sync to REP state.
[all...] |
| /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
39 These files will follow existing convention concerning the location of source
40 and installed files. All source files will be in src/tools/stf/contrib/smf (a
42 ${STF_TOOLS}/contrib/smf/include/libsmf.shlib, and the invocable commands will
54 For compatibility sake, the library functions will all conform to Bourne Shell
71 # Will return 0 if smf appears to be installed and should be
72 # usable, otherwise it will return != 0.
74 # This function will check and rely on the presence or absenc
[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
39 These files will follow existing convention concerning the location of source
40 and installed files. All source files will be in src/tools/stf/contrib/smf (a
42 ${STF_TOOLS}/contrib/smf/include/libsmf.shlib, and the invocable commands will
54 For compatibility sake, the library functions will all conform to Bourne Shell
71 # Will return 0 if smf appears to be installed and should be
72 # usable, otherwise it will return != 0.
74 # This function will check and rely on the presence or absenc
[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
39 These files will follow existing convention concerning the location of source
40 and installed files. All source files will be in usr/src/tools/genutils/smf (a
42 $STC_GENUTILS/include/libsmf.shlib, and the invocable commands will be in
55 For compatibility sake, the library functions will all conform to Bourne Shell
72 # Will return 0 if smf appears to be installed and should be
73 # usable, otherwise it will return != 0.
75 # This function will check and rely on the presence or absenc
[all...] |
| /test/ohacts/src/tset/geo/doc/ |
| README | 36 1st failover address that testsuite will use for 1st sndr set
41 2nd failover address that testsuite will use for 2nd sndr set
46 3rd failover address that testsuite will use for 1st HA-NFS
51 4th failover address that testsuite will use for 2nd HA-NFS
57 will use for 1st sndr set on primary cluster.
63 will use for 2nd sndr set on primary cluster.
73 1st failover address that testsuite will use for 1st sndr set
78 2nd failover address that testsuite will use for 2nd sndr set
83 3rd failover address that testsuite will use for 1st HA-NFS
88 4th failover address that testsuite will use for 2nd HA-NF
[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/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/lofi/ |
| STATUS.LIST | 35 Some tests will return a status of 'UNTESTED', meaning that no attempt
45 - Setting RUNMODE to 'medium' or 'short' will result in 'UNTESTED'
51 algorithms) will result in 'UNTESTED' being returned for a variety of
57 named zone. When run in the global zone, this test will report
59 the named zones test in a non-global zone will result in failures.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/scope/scf_handle_get_local_scope/ |
| ASSERTIONS | 43 will be deleted from libscf
56 will be deleted from libscf.
76 According to jwadams, this function will be deleted from libscf
|
| /test/ontest-stc2/src/tools/stf/contrib/backup/doc/ |
| README.backup_files | 32 backup_files.kshlib are very picky. When given unexpected input, they will
38 the same file will fail
40 - backing up a symbolic link will backup _both_ the link and the data
45 the file will be deleted if it exists. This could be used simply
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/scope/scf_handle_get_local_scope/ |
| ASSERTIONS | 43 will be deleted from libscf
56 will be deleted from libscf.
76 According to jwadams, this function will be deleted from libscf
|
| /test/stcnv/usr/src/tools/stf/contrib/backup/doc/ |
| README.backup_files | 32 backup_files.kshlib are very picky. When given unexpected input, they will
38 the same file will fail
40 - backing up a symbolic link will backup _both_ the link and the data
45 the file will be deleted if it exists. This could be used simply
|
| /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.
|
| /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.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/connection/scf_handle_unbind/ |
| ASSERTIONS | 33 scf_handle_unbind() will return -1 and set the error code to
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/security/smf_security_errors/ |
| README | 34 single one of said modifications will fail. See smf_security(5).
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/connection/scf_handle_unbind/ |
| ASSERTIONS | 33 scf_handle_unbind() will return -1 and set the error code to
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/security/smf_security_errors/ |
| README | 34 single one of said modifications will fail. See smf_security(5).
|
