2011-06-12 20:57:14 +00:00
|
|
|
zsh-syntax-highlighting / tests
|
|
|
|
===============================
|
|
|
|
|
|
|
|
Utility scripts for testing zsh-syntax-highlighting highlighters.
|
|
|
|
|
2015-11-16 22:31:18 +00:00
|
|
|
The tests harness expects the highlighter directory to contain a `test-data`
|
|
|
|
directory with test data files.
|
|
|
|
See the [main highlighter](../highlighters/main/test-data) for examples.
|
2011-06-12 20:57:14 +00:00
|
|
|
|
2015-09-12 20:29:04 +00:00
|
|
|
Each test should define the array parameter `$expected_region_highlight`.
|
2015-11-17 03:02:39 +00:00
|
|
|
The value of that parameter is a list of strings of the form `"$i $j $style"`.
|
|
|
|
or `"$i $j $style $todo"`.
|
2015-09-12 20:29:04 +00:00
|
|
|
Each string specifies the highlighting that `$BUFFER[$i,$j]` should have;
|
|
|
|
that is, `$i` and `$j` specify a range, 1-indexed, inclusive of both endpoints.
|
2015-11-17 03:02:39 +00:00
|
|
|
If `$todo` exists, the test point is marked as TODO (the failure of that test
|
|
|
|
point will not fail the test), and `$todo` is used as the explanation.
|
2015-09-12 20:29:04 +00:00
|
|
|
|
2015-11-17 03:02:39 +00:00
|
|
|
**Note**: `$region_highlight` uses the same `"$i $j $style"` syntax but
|
|
|
|
interprets the indexes differently.
|
2015-09-12 20:29:04 +00:00
|
|
|
|
2015-11-17 03:02:39 +00:00
|
|
|
**Isolation**: Each test is run in a separate subshell, so any variables,
|
|
|
|
aliases, functions, etc., it defines will be visible to the tested code (that
|
|
|
|
computes `$region_highlight`), but will not affect subsequent tests. The
|
|
|
|
current working directory of tests is set to a newly-created empty directory,
|
2015-11-16 22:54:52 +00:00
|
|
|
which is automatically cleaned up after the test exits.
|
2015-11-16 22:31:18 +00:00
|
|
|
|
2011-06-12 20:57:14 +00:00
|
|
|
|
2015-11-17 03:25:03 +00:00
|
|
|
Highlighting test
|
2011-06-12 20:57:14 +00:00
|
|
|
-----------------
|
2015-11-17 02:54:53 +00:00
|
|
|
|
2015-11-17 03:02:39 +00:00
|
|
|
[`test-highlighting.zsh`](tests/test-highlighting.zsh) tests the correctness of
|
|
|
|
the highlighting. Usage:
|
2011-06-12 20:57:14 +00:00
|
|
|
|
|
|
|
zsh test-highlighting.zsh <HIGHLIGHTER NAME>
|
|
|
|
|
2015-10-23 03:27:05 +00:00
|
|
|
All tests may be run with
|
|
|
|
|
|
|
|
make test
|
|
|
|
|
2015-11-17 03:02:39 +00:00
|
|
|
which will run all highlighting tests and report results in [TAP format][TAP].
|
2016-01-02 21:22:01 +00:00
|
|
|
By default, the results of all tests will be printed; to show only "interesting"
|
|
|
|
results (tests that failed but were expected to succeed, or vice-versa), run
|
|
|
|
`make quiet-test` (or `make test QUIET=y`).
|
2015-11-17 03:02:39 +00:00
|
|
|
|
|
|
|
[TAP]: http://testanything.org/
|
2015-10-23 03:27:05 +00:00
|
|
|
|
2011-06-12 20:57:14 +00:00
|
|
|
|
2015-11-17 03:25:03 +00:00
|
|
|
Performance test
|
2011-06-12 20:57:14 +00:00
|
|
|
----------------
|
2015-11-17 02:54:53 +00:00
|
|
|
|
2015-11-17 03:02:39 +00:00
|
|
|
[`test-perfs.zsh`](tests/test-perfs.zsh) measures the time spent doing the
|
|
|
|
highlighting. Usage:
|
2011-06-12 20:57:14 +00:00
|
|
|
|
|
|
|
zsh test-perfs.zsh <HIGHLIGHTER NAME>
|
2015-10-27 07:46:51 +00:00
|
|
|
|
|
|
|
All tests may be run with
|
|
|
|
|
|
|
|
make perf
|