| /test/stcnv/usr/src/suites/storage/fwflash/ |
| STATUS.LIST | 33 known defects. However, no 'UNRESOLVED', since on some test cases,
36 the value to the variable(which is allowed), those test cases will
48 The 'UNINITIATED' result on above 6 cases is due to no device path given
49 to "FWDEV2" so that the test cases simply return with 'UNINITIATED'
|
| README | 52 In the majority of cases, the test suite can be installed from packages.
161 cases)
|
| /test/ontest-stc2/src/suites/os/xvm/virt-install/ |
| README.CONFIG | 49 test_config.solaris - config file to run solaris pv test cases. pxe,
50 linux and simultaneous test cases are not run.
56 test_config.fullrun - config file which will run all test cases in the
57 suite. Configured for linux, pxe and simultaneous test cases.
|
| /test/stcnv/usr/src/suites/os/lofi/ |
| STATUS.LIST | 37 are configured. Due to the dynamic generation of test cases in the
46 being returned for test cases involving large file sizes.
52 test cases.
68 These are due to negative test cases being run and do not indicate
|
| /test/stcnv/usr/src/suites/os/xvm/virt-install/ |
| README.CONFIG | 41 run the Linux and PXE test cases, the local DHCP server will need to
50 test_config.fullrun - config file which will run all test cases in the
51 suite. Configured for linux, pxe, nfs and simultaneous test cases.
91 # Linux test cases. See the README file for information on setting up
|
| README | 73 In the majority of cases, the test suite can be installed from packages. The
|
| /test/ontest-stc2/src/suites/nfs/sharemnt/tests/nfslogd/ |
| README | 58 - All test cases are named by prefix "NFSLOGD" combining
68 files to serialize all cases in all clients to run one by
78 pid : One case is running, other cases aren't allowed to
|
| /test/ontest-stc2/src/tools/stf/include/ |
| testgen.kshlib | 38 # programs. In order to use dynamic test cases in STF, one needs to write a
41 # dynamic test cases are similar in construction and content: several big
45 # test cases in STF.
55 # -m: true -- Create test cases, and put the composed lines to
57 # false -- Put the composed line to the stdout only, no cases
60 # -u: root -- Create root test cases,
61 # otherwise create user test cases.
67 # caseline -- A set of test cases were defined in one line.
71 # caseblock -- A set of test cases were defined in one block.
101 # will be eval'ed before the target cases generated from the
[all...] |
| /test/stcnv/usr/src/suites/nfs/sharemnt/tests/nfslogd/ |
| README | 58 - All test cases are named by prefix "NFSLOGD" combining
68 files to serialize all cases in all clients to run one by
78 pid : One case is running, other cases aren't allowed to
|
| /test/stcnv/usr/src/tools/stf/include/ |
| testgen.kshlib | 38 # programs. In order to use dynamic test cases in STF, one needs to write a
41 # dynamic test cases are similar in construction and content: several big
45 # test cases in STF.
55 # -m: true -- Create test cases, and put the composed lines to
57 # false -- Put the composed line to the stdout only, no cases
60 # -u: root -- Create root test cases,
61 # otherwise create user test cases.
67 # caseline -- A set of test cases were defined in one line.
71 # caseblock -- A set of test cases were defined in one block.
101 # will be eval'ed before the target cases generated from the
[all...] |
| /test/ontest-stc2/src/tools/stf/bin/ |
| mstf_addassert.ksh | 46 All tests cases added via this command will execute as root, because
|
| /test/stcnv/usr/src/tools/stf/bin/ |
| mstf_addassert.ksh | 46 All tests cases added via this command will execute as root, because
|
| /test/ontest-stc2/src/tools/tet/contrib/ctitools/ |
| README | 185 This enhancement provides facilities for TET test cases to be written and run
210 cases.
211 Kernel test cases look very similar to TET user-level test cases. They can
213 cases are kernel modules which run directly in the kernel, and they can be
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
265 This allows you to write test cases that run directly in the kernel and yet
280 with each other when accessing global kernel resources). And kernel test cases
281 can be mixed and matched with userland test cases, for example
[all...] |
| /test/stcnv/usr/src/tools/tet/contrib/ctitools/ |
| README | 199 This enhancement provides facilities for TET test cases to be written and run
224 cases.
225 Kernel test cases look very similar to TET user-level test cases. They can
227 cases are kernel modules which run directly in the kernel, and they can be
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
279 This allows you to write test cases that run directly in the kernel and yet
294 with each other when accessing global kernel resources). And kernel test cases
295 can be mixed and matched with userland test cases, for example
[all...] |
| /test/ohacts/src/doc/dataservice/ |
| README | 29 This file has information on all the test cases in this test suite
34 1) testcases file : It has a list of all the test cases in DATS
|
| /test/ontest-stc2/src/suites/iSCSI/ |
| README | 54 In the majority of cases, the test suite can be installed from packages. The
79 In the majority of cases, the test suite can be installed from packages. The
|
| /test/ontest-stc2/src/suites/share/ |
| README | 47 In the majority of cases, the test suite can be installed from packages. The
71 In the majority of cases, the test suite can be installed from packages. The
|
| /test/stcnv/usr/src/tools/genutils/ |
| README | 55 In the majority of cases, the STC GenUtils tool can be installed
137 something went wrong. In most cases, these message should be enough
140 In some cases, however, if those information is not enough, or if one
|
| /test/ontest-stc2/src/suites/os/smf/ |
| README | 37 o In the majority of cases, the test suite can be installed from packages. The
122 o To execute only test cases in a specific directory:
|
| /test/ontest-stc2/src/suites/os/smf/tests/libscf-low/trans/scf_transaction_add/ |
| ASSERTIONS | 152 proved by all the other scf_transaction_add* test cases as well
|
| /test/stcnv/usr/src/suites/net/nc/ |
| README | 265 TCP port such as those in vflag or pflag test cases. Same rules apply w.r.t.
288 listen_wrapper() or start_nc(). In some cases it is needed to execute
289 it directly. In such cases it should be started like this:
396 Assuming all test cases/purposes use these functions it should be easy to
|
| /test/stcnv/usr/src/suites/os/smf/ |
| README | 53 o In the majority of cases, the test suite can be installed from
141 o To execute only test cases in a specific directory:
|
| /test/stcnv/usr/src/suites/os/smf/tests/libscf-low/trans/scf_transaction_add/ |
| ASSERTIONS | 152 proved by all the other scf_transaction_add* test cases as well
|
| /test/stcnv/usr/src/tools/tet/contrib/tetreport/ |
| tetreport.pl | 61 -s Summary report detailing the test cases run and the pass rate
|
| /test/ohacts/src/tset/dataservice/scripts/ |
| verify_rg_offline.ksh | 460 # of processes. This isn't working very well in some cases.
|
