vieter-v
/
v
2
0
Fork 0
Code Issues Pull Requests Releases Activity

help: improve `v help test`

pull/12917/head weekly.2021.51
Delyan Angelov 2021-12-20 19:52:05 +02:00
parent 460f7c6637
commit ed2d1286da
No known key found for this signature in database
GPG Key ID: 66886C0F12D595ED
1 changed files with 35 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
cmd/v/help/test.txt
View File

@ -1,13 +1,24 @@
Usage: Usage:
v [-stats] test FILE|DIRECTORY[...] v [-stats] test FILE|DIRECTORY[...] [-run-only GPATTERN1[,...]]
Runs test functions in the given FILEs and DIRECTORYs Runs test functions in the given FILEs and DIRECTORYs.
If '-stats' is given, more statistics about the tests are printed along If '-stats' is given, more statistics about the tests are printed along
with a report of passes/failures with a report of passes/failures
If you give `-run-only GPATTERN`, then *only* test functions, that do
match by name the given glob pattern `GPATTERN` will run. You can separate
multiple glob patterns with `,`.
If a _test.v file lacks matching functions for all of the glob patterns, it
will be ignored completely, so you can do in effect:
`v test . -run-only test_your_fn_name`
... and V will run only that test function, no matter how many _test.v
files you have, and how many other test_ functions exist in them.
NB: glob patterns support `*` which matches anything, and `?`, that
matches any single character. They are *NOT* regular expressions however.
NB 1: very frequently, when you work on a module you can cd into its folder, NB 1: very frequently, when you work on a module you can cd into its folder,
and then you can perform: and then you can perform:
v test . v test .
... to run all the module's '_test.v' files. ... to run all the module's '_test.v' files.
NB 2: V builtin testing requires you to name your files with a _test.v NB 2: V builtin testing requires you to name your files with a _test.v
@ -24,10 +35,28 @@ You can use several alternative test result formats, using `-test-runner name`,
or by setting VTEST_RUNNER (the command line option has higher priority). or by setting VTEST_RUNNER (the command line option has higher priority).
The names of the available test runners are: The names of the available test runners are:
`simple` Fastest, does not import additional modules, does no processing. `simple` Fastest, does not import additional modules, does no processing.
`tap` Format the output as required by the Test Anything Protocol (TAP). `tap` Format the output as required by the Test Anything Protocol (TAP).
`normal` Supports color output, nicest/most human readable, the default. `normal` Supports color output, nicest/most human readable, the default.
You can also implement your own custom test runner, by providing the path to You can also implement your own custom test runner, by providing the path to
your .v file, that implements it to this option. For example, see: your .v file, that implements it to this option. For example, see:
vlib/v/preludes/test_runner_tap.v . vlib/v/preludes/test_runner_tap.v .
NB 5: Filtering only specific _test.v files by name:
You can set the environment variable `VTEST_ONLY` to a list of strings, that
will have to be contained in the paths of the _test.v files.
Example:
`VTEST_ONLY=complex,stats v test . -run-only *sin*`
This will find all _test.v files that have either `complex` or `stats`
in their path, then for these test files, V test will find all that contain
`test_` functions that glob match `*sin*`, and run only them, so you
should see something like this:
```
OK [1/2] 164.671 ms vlib/math/stats/stats_test.v
OK [2/2] 184.842 ms vlib/math/complex/complex_test.v
------------------------------------------------------------------------------------------
Summary for all V _test.v files: 2 passed, 2 total. Runtime: 185 ms, on 2 parallel jobs.
```