| /test/stcnv/usr/src/tools/tet/contrib/php-cli_api/ |
| phptet_dyn.php | 23 foreach ($php_testlist as $testic => $value)
42 foreach ($php_testlist as $testic => $value)
57 foreach ($php_testlist as $testic => $value)
72 foreach ($php_testlist as $testic => $value)
87 foreach ($php_testlist as $testic => $value)
102 foreach ($php_testlist as $testic => $value)
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/instance/scf_instance_destroy/ |
| ASSERTIONS | 44 scf_instance_destroy() silently accepts the NULL pointer as
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/instance/scf_instance_destroy/ |
| ASSERTIONS | 44 scf_instance_destroy() silently accepts the NULL pointer as
|
| /test/ontest-stc2/src/tools/stf/contrib/jnl/include/ |
| jnl_proto.h | 43 * jnl_dl_fetch() returns the value of the detail level as of the first
159 * non-zero value by the function, such as write(), which failed.
161 * returned as if the message was committed to the journal.
187 * <text> is the concatenation of all the text strings passed [as va_args]
237 * int Same return values as jnl_LOG().
241 * message will be formatted as follows:
258 #define jnl_ASSERTION(as, in) (jnl_LOG(jnlDL_ASSERTION, \
266 as, \
289 * int Same return values as jnl_LOG().
293 * message will be formatted as follows
[all...] |
| /test/stcnv/usr/src/tools/stf/contrib/jnl/include/ |
| jnl_proto.h | 43 * jnl_dl_fetch() returns the value of the detail level as of the first
159 * non-zero value by the function, such as write(), which failed.
161 * returned as if the message was committed to the journal.
187 * <text> is the concatenation of all the text strings passed [as va_args]
237 * int Same return values as jnl_LOG().
241 * message will be formatted as follows:
258 #define jnl_ASSERTION(as, in) (jnl_LOG(jnlDL_ASSERTION, \
266 as, \
289 * int Same return values as jnl_LOG().
293 * message will be formatted as follows
[all...] |
| /test/stcnv/usr/src/tools/tet/contrib/demo/tset/test1/ |
| nt.mk | 2 # for Windows NT, we need to use .exe, .obj, .lib as appropriate
14 # when using Distributed TETware on systems such as SVR4 and Solaris
|
| /test/ohacts/src/tset/dataservice/doc/assertions/ |
| dataservice_reboot | 38 3. Failback property of the resource group should work as expected.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/service/scf_service_destroy/ |
| ASSERTIONS | 45 scf_service_destroy() silently accepts the NULL pointer as the
|
| /test/stcnv/usr/src/suites/nfs/nfsgen/tests/recovery/ |
| README | 35 start processes on different machine (such as CLIENT and CLIENT2). In
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/service/scf_service_destroy/ |
| ASSERTIONS | 45 scf_service_destroy() silently accepts the NULL pointer as the
|
| /test/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/get_port_list/ |
| ASSERTIONS | 76 DESCRIPTION: There should be a failure if NULL is passed as first parameter
83 2. Pass NULL as the first paramter to FCOE_GetPortList().
98 DESCRIPTION: There should be a failure if NULL is passed as second parameter
105 2. Pass NULL as the second paramter to FCOE_GetPortList().
|
| /test/ontest-stc2/src/tools/tet/contrib/ctitools/ |
| README | 43 src/utils - the CTI command line utility and it's associated tools. As well
44 as the build, clean and exec tools, the kmodtool interface and setuid programs
172 The build_tool and clean_tool scripts can be used as TCC build and clean tools
192 tools such as make can still be used.
214 specified in the same scenarios as user-level test cases.
221 Kernel test cases must include the header file <tet_kmodapi.h> (as opposed to
223 They must also be linked with the archive library likmodapi.a (as opposed to
226 The file kmodtool.c is a "fake" user-level test case which acts as a
228 the $CTI_ROOT/bin/exec_tool script as the TCC exec tool. This can be done
229 by adding an entry such as
[all...] |
| /test/stcnv/usr/src/tools/tet/contrib/ctitools/ |
| README | 49 src/utils - the CTI command line utility and it's associated tools. As well
50 as the build, clean and exec tools, the kmodtool interface and setuid programs
186 The build_tool and clean_tool scripts can be used as TCC build and clean tools
206 tools such as make can still be used.
228 specified in the same scenarios as user-level test cases.
235 Kernel test cases must include the header file <tet_kmodapi.h> (as opposed to
237 They must also be linked with the archive library likmodapi.a (as opposed to
240 The file kmodtool.c is a "fake" user-level test case which acts as a
242 the $CTI_ROOT/bin/exec_tool script as the TCC exec tool. This can be done
243 by adding an entry such as
[all...] |
| /test/ontest-stc2/src/tools/stf/etc/ |
| BuildConfig.master | 48 # characters (spaces and tabs) behave as a single separator.
55 # Denotes a non-applicable field to be returned as a null
132 # fewer of these used as keys in the table, the tighter they
137 # Denotes a non-applicable field to be returned as a null
182 sparc as as /usr/ccs/bin {na}
184 sparc-f64 as as /usr/ccs/bin {na}
186 sparcv9 as as /usr/ccs/bin -xarch=v
[all...] |
| /test/stcnv/usr/src/tools/stf/etc/ |
| BuildConfig.master | 48 # characters (spaces and tabs) behave as a single separator.
55 # Denotes a non-applicable field to be returned as a null
132 # fewer of these used as keys in the table, the tighter they
137 # Denotes a non-applicable field to be returned as a null
182 sparc as as /usr/ccs/bin {na}
184 sparc-f64 as as /usr/ccs/bin {na}
186 sparcv9 as as /usr/ccs/bin -xarch=v
[all...] |
| /test/stcnv/usr/src/tools/tet/contrib/demo110/ts/ |
| nt.mk | 2 # for Windows NT, we need to use .exe, .obj, .lib as appropriate
14 # when using Distributed TETware on systems such as SVR4 and Solaris
|
| /test/ontest-stc2/src/tools/stf/bin/ |
| mstf_addassert.ksh | 46 All tests cases added via this command will execute as root, because
47 the mstf_launch script runs as root.
|
| /test/stcnv/usr/src/tools/stf/bin/ |
| mstf_addassert.ksh | 46 All tests cases added via this command will execute as root, because
47 the mstf_launch script runs as root.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/snaplevel/scf_snaplevel_create/ |
| ASSERTIONS | 39 2. Reduce the VMEM rlimit of the child process to as small as
40 value as possible.
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/snaplevel/scf_snaplevel_create/ |
| ASSERTIONS | 39 2. Reduce the VMEM rlimit of the child process to as small as
40 value as possible.
|
| /test/stcnv/usr/src/suites/os/cpu-caps/ |
| README | 41 Some of the tests examine the behavior of processes under a zone cap. As a
43 zone cap. Measures have been made to mitigate this as much as possible, but
48 won't be in run in ONPIT as they have this higher propensity for false failure.
55 As a final note, the fewer CPUs a system has, the higher the likelihood of
68 This suite should not be executed in a local zone as the suite creates its own
70 /export/test_zone as its root directory and upon test suite completion, should
77 As root user perform the following to install the tetlite and cpu-caps test
125 The lowest level entity that can be executed is the "invocable component" as
136 The test suite build should not be done as root user
[all...] |
| /test/stcnv/usr/src/suites/fs/cifs-client/ |
| README | 55 User must run the test suite as root
71 c. Make sure the user has rsh access to server as root
77 on any system can remote-login to the CIFS server as root)
107 - obtain the test suite source as a non-root user
137 - obtain the test suite source as a non-root user
202 - Create user cifs_user and use "C_sun_123" as its password
203 - Create user cifs_user1 and use "C_sun_123" as its password
204 - Create user a_share and use "A_sun_123" as its password
205 - Create user b_share and use "B_sun_123" as its password
231 - Create user cifs_user and use "C_sun_123" as its passwor
[all...] |
| /test/stcnv/usr/src/suites/storage/comstar/ |
| README | 60 After downloading the package, as root do the following:
77 After downloading the package, as root do the following:
86 test suite, as root do:
97 build the test suite source, as any user, do:
144 configuration information such as target group, host group, view entry
162 as they become qualified and supported for Comstar.
166 Test suite configuration must be done as root.
185 The configuration file will be created as a result of the arguments specified
217 The test suite execution is required to be done as root.
262 configuration information such as target group, host group, view
[all...] |
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/delegation/ |
| README | 59 To run individual assertions, first you need to setup the machines manually, as
64 # (set the appropriate environment variables, as the minimum
76 or # cd delegation; ./runtests (same as above)
77 You can repeat these steps as many times as needed. Results will be overwritten.
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/pg/scf_pg_get_underlying_pg/ |
| ASSERTIONS | 46 name as the input property group is found.
126 a service of the same name as the input pg's parent service,
151 has a service of the same name as the input pg's parent service,
152 but that service does not have a pg of the same name as the input
177 has a service of the same name as the input pg's parent service,
178 and at least one of these services has a pg of the same name as
|
