Lines Matching +full:- +full:- +full:with +full:- +full:zstd

3 The CLI tests are focused on testing the zstd CLI.
10 …er `run.py` will run tests against the in-tree build of `zstd` and `datagen` by default. Which mea…
12 The `zstd` binary used can be passed with `--zstd /path/to/zstd`.
13 Additionally, to run `zstd` through a tool like `valgrind` or `qemu`, set the `--exec-prefix 'valgr…
15 Similarly, the `--datagen`, and `--zstdgrep` flags can be set to specify
19 …mally these directories are removed after the test executes. However, the `--preserve` flag will p…
29 ./run.py --preserve
30 ./run.py --zstd ../../build/programs/zstd --datagen ../../build/tests/datagen
36 This can be useful for writing or debugging a test, especially with `--preserve`.
44 ./run.py --preserve basic/help.sh basic/version.sh
45 ./run.py --preserve --verbose basic/help.sh
50 …derr.exact` or `.stdout.exact` no longer matches, you can re-run the tests with `--set-exact-outpu…
54 ./run.py --set-exact-output
55 ./run.py basic/help.sh --set-exact-output
63 …e files. This directory will be cleaned up at the end of the test, unless `--preserve` is passed t…
65 ### Calling zstd, utilities, and environment variables
67 The `$PATH` for tests is prepended with the `bin/` sub-directory, which contains helper scripts for…
68 The `zstd` binary will call the zstd binary specified by `run.py` with the correct `$EXEC_PREFIX`.
73 …cript libraries are provided under `common/`, with helper variables and functions. They can be sou…
75 …ent variables are provided for testing, which can be listed when calling `run.py` with `--verbose`.
88 If you provide a `.exact` file, the output is expected to exactly match, byte-for-byte.
101 exit-1.sh
102 ---
105 ---
107 exit-1.sh.exit
108 ---
110 ---
117 ---
120 ---
123 ---
125 ---
132 ---
134 head -c 10 < /dev/urandom | xxd >&2
135 ---
138 ---
142 Multiple lines can be matched with ...
145 random-num-lines.sh
146 ---
151 ---
153 random-num-lines.sh.stdout.glob
154 ---
159 ---
167 exit-1.sh
168 ---
171 ---
178 ---
187 ---
190 ---
193 ---
195 ---
200 Finally, test writing can be eased with setup and teardown scripts.
201 …h directory in the test directory is a test-suite consisting of all tests within that directory (b…
202 This test suite can come with 4 scripts to help test writing:
222 ---
224 # Create some files for testing with
228 ---
231 ---
233 zstd file file0 file1
234 ---
237 ---
239 set -e
243 	datagen -g1000 > files/$i
246 zstd --train -r files/ -o dicts/0
247 ---
250 ---
256 cp -r ../files ../dicts .
257 ---