README.md (681ce946f33e75c590e97c53076e86dff1fe8f4a) README.md (716fd348e01c5f2ba125f878a634a753436c2994)
1# ZFS Test Suite README
2
3### 1) Building and installing the ZFS Test Suite
4
5The ZFS Test Suite runs under the test-runner framework. This framework
6is built along side the standard ZFS utilities and is included as part of
7zfs-test package. The zfs-test package can be built from source as follows:
8

--- 25 unchanged lines hidden (view full) ---

34 * A non-root user with a full set of basic privileges and the ability
35 to sudo(8) to root without a password to run the test.
36 * Specify any pools you wish to preserve as a space delimited list in
37 the $KEEP variable. All pools detected at the start of testing are
38 added automatically.
39 * The ZFS Test Suite will add users and groups to test machine to
40 verify functionality. Therefore it is strongly advised that a
41 dedicated test machine, which can be a VM, be used for testing.
1# ZFS Test Suite README
2
3### 1) Building and installing the ZFS Test Suite
4
5The ZFS Test Suite runs under the test-runner framework. This framework
6is built along side the standard ZFS utilities and is included as part of
7zfs-test package. The zfs-test package can be built from source as follows:
8

--- 25 unchanged lines hidden (view full) ---

34 * A non-root user with a full set of basic privileges and the ability
35 to sudo(8) to root without a password to run the test.
36 * Specify any pools you wish to preserve as a space delimited list in
37 the $KEEP variable. All pools detected at the start of testing are
38 added automatically.
39 * The ZFS Test Suite will add users and groups to test machine to
40 verify functionality. Therefore it is strongly advised that a
41 dedicated test machine, which can be a VM, be used for testing.
42 * On FreeBSD, mountd(8) must use `/etc/zfs/exports`
43 as one of its export files – by default this can be done by setting
44 `zfs_enable=yes` in `/etc/rc.conf`.
42
43Once the pre-requisites are satisfied simply run the zfs-tests.sh script:
44
45 $ /usr/share/zfs/zfs-tests.sh
46
47Alternately, the zfs-tests.sh script can be run from the source tree to allow
48developers to rapidly validate their work. In this mode the ZFS utilities and
49modules from the source tree will be used (rather than those installed on the

--- 33 unchanged lines hidden (view full) ---

83 be skipped which depend on real block devices.
84
85 -c Only create and populate constrained path
86
87 -I NUM Number of iterations
88
89 -d DIR Create sparse files for vdevs in the DIR directory. By
90 default these files are created under /var/tmp/.
45
46Once the pre-requisites are satisfied simply run the zfs-tests.sh script:
47
48 $ /usr/share/zfs/zfs-tests.sh
49
50Alternately, the zfs-tests.sh script can be run from the source tree to allow
51developers to rapidly validate their work. In this mode the ZFS utilities and
52modules from the source tree will be used (rather than those installed on the

--- 33 unchanged lines hidden (view full) ---

86 be skipped which depend on real block devices.
87
88 -c Only create and populate constrained path
89
90 -I NUM Number of iterations
91
92 -d DIR Create sparse files for vdevs in the DIR directory. By
93 default these files are created under /var/tmp/.
94 This directory must be world-writable.
91
92 -s SIZE Use vdevs of SIZE (default: 4G)
93
94 -r RUNFILES Run tests in RUNFILES (default: common.run,linux.run)
95
96 -t PATH Run single test at PATH relative to test suite
97
98 -T TAGS Comma separated list of tags (default: 'functional')

--- 159 unchanged lines hidden --- 		95
96 -s SIZE Use vdevs of SIZE (default: 4G)
97
98 -r RUNFILES Run tests in RUNFILES (default: common.run,linux.run)
99
100 -t PATH Run single test at PATH relative to test suite
101
102 -T TAGS Comma separated list of tags (default: 'functional')

--- 159 unchanged lines hidden ---