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

1 2 3

  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/acl/cmd_tests/
README 31 This sub-suite consists of command tests for testing NFSv4 ACL.
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/acl/cmd_tests/
README 31 This sub-suite consists of command tests for testing NFSv4 ACL.
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/ctests/
README 31 This sub-suite consists of tests for testing NFSv4 operations using syscall
  /test/ontest-stc2/src/suites/zfs/tests/functional/cli_root/zpool_upgrade/blockfiles/
README 32 This directory contains compressed blockfiles for zpool upgrade testing.
  /test/stcnv/usr/src/suites/fs/zfs/tests/functional/cli_root/zpool_upgrade/blockfiles/
README 32 This directory contains compressed blockfiles for zpool upgrade testing.
  /test/stcnv/usr/src/suites/net/driver-wifi/doc/assertions/configure/
configure.assert 34 Check the testing environment for IBSS.
52 The testing WiFi link $TEST_IF in config file exists locally.
55 The testing WiFi link $RMT_TEST_IF in config file exists
60 The testing WiFi link support to create ad hoc network.
64 The testing WiFi link support to create ad hoc network.
  /test/stcnv/usr/src/suites/net/driver-wifi/doc/assertions/unconfigure/
unconfigure.assert 34 Unconfigure the testing environment for IBSS.
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/
README 38 There are also ksh script testing the nfsmapid domain and NFSv4 providers.
  /test/stcnv/usr/src/suites/nfs/nfsgen/tests/recovery/
README 37 For best testing, it's better to make each process access a different
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/
README 38 There are also ksh script testing the nfsmapid domain and NFSv4 providers.
  /test/ontest-stc2/src/suites/storage/megacli/doc/
megacli.assertion 72 1. If there is only one disk available, use one disk or testing, If there are more than one disk available, use two disks for testing;
105 1. If there is only one disk available, use one disk or testing, If there are more than one disk available, use two disks for testing;
141 1. If there is only one disk available, use one disk or testing, If there are more than one disk available, use two disks for testing;
172 1. If there is only one disk available, use one disk or testing, If there are more than one disk available, use two disks for testing;
173 2. Run "MegaCli -CfgLdAdd -R0[E0:S0,E1:S1] -szXXX -aN" where XXX great than the total capacity of the testing disks;
201 1. If there is only one disk available, use one disk or testing, If there are more than one disk available, use two disks for testing
    [all...]
  /test/stcnv/usr/src/suites/storage/fwflash/
STATUS.LIST 35 given to FWDEV2 variable for testing, if test engineer didn't give
  /test/ontest-stc2/src/suites/storage/megacli/
README 34 megacli is a test suite for mega_sas driver regression testing. It will use
42 1. One LSI MegaRAID SAS 1078 based controller as the testing target.
74 You can install the test suite on the system under testing, or at a network
75 location which is accessible by the system under testing.
114 Warning: the execution of this test suite will destroy all data on testing
115 disks. Make sure the disks available for the testing adapter do not have
131 testing controller. Make sure the testing controller do not have any useful
  /test/stcnv/usr/src/suites/storage/megacli/doc/
megacli.assertion 43 3. Run "prtconf -DP" to check if the device node listed in the devices tree which driven by the testing driver;
72 1. If there is only one disk available, use one disk for testing, If there are more than one disk available, use two disks for testing;
111 1. If there is only one disk available, use one disk for testing, If there are more than one disk available, use two disks for testing;
147 1. If there is only one disk available, use one disk for testing, If there are more than one disk available, use two disks for testing;
148 2. Run "MegaCli -CfgLdAdd -R0[E0:S0,E1:S1] -szXXX -aN" where XXX great than the total capacity of the testing disks;
176 1. If there is only one disk available, use one disk for testing, If there are more than one disk available, use two disks for testing;
    [all...]
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/server/
README 49 installed in server systems which maybe outside the testing
  /test/stcnv/usr/src/suites/nfs/nfsv4/server/
README 49 installed in server systems which maybe outside the testing
  /test/stcnv/usr/src/tools/diskomizer/
README 31 Diskomizer is a program for testing and verifying disk subsystems.
37 read only testing of devices; providing a non destructive method of
38 testing.
98 Testing Diskomizer
105 More extensive testing can be done using virtual targets that can be
  /test/ontest-stc2/src/tools/stf/
README 43 * Support for assertion-based testing and standard result codes
53 * Support for table-driven testing and automated test case generation
  /test/stcnv/usr/src/suites/storage/megacli/
README 35 megacli is a test suite for mega_sas driver regression testing. It uses
46 1. One LSI MegaRAID SAS 1078 based controller as the testing target.
82 You can install the test suite on the system under testing, or at a
124 disks used for testing. Make sure the disks available for the testing
140 testing controller. Make sure the testing controller do not have any useful
  /test/stcnv/usr/src/tools/stf/
README 43 * Support for assertion-based testing and standard result codes
53 * Support for table-driven testing and automated test case generation
  /test/ontest-stc2/src/suites/net/nicdrv/doc/
nicdrv.assert 235 - Start single session TCP/UDP testing on test interfaces
324 - After the testing, the test interface should still work (no hang).
348 - Find the attachment ponit id for the NIC card under testing
378 - After 12-15 hours of testing, the test interface should still work
410 - After the testing, the test interface should still work (no hang).
  /test/ontest-stc2/src/suites/storage/sdts/
README 32 HBA driver function testing and SMP expander driver function testing.
39 http://www.opensolaris.org/os/community/testing/testsuites/ctifortet/
52 To run SMP test cases, you must copy lsiutil binary to testing platform.
  /test/stcnv/usr/src/suites/net/nicdrv/doc/
nicdrv.assert 235 - Start single session TCP/UDP testing on test interfaces
324 - After the testing, the test interface should still work (no hang).
348 - Find the attachment ponit id for the NIC card under testing
406 NIC driver parameter configuration testing via dladm command(Brussles project)
440 - After 12-15 hours of testing, the test interface should still work
472 - After the testing, the test interface should still work (no hang).
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/
README 33 testing NFSv4 server and client. Test sub-directories include :
128 There are several test filesystems required for testing.
151 BASEDIR the base testing directory, default is /NFSv4Test
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/domain/
README 31 This sub-suite consists of tests for testing rules to get the domain for

Completed in 780 milliseconds

1 2 3