|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | 03-May-2022 | - |
| a/ | H | 16-Oct-2021 | - | 914 | 823 |
| b/ | H | 16-Oct-2021 | - | 581 | 538 |
| c/ | H | 16-Oct-2021 | - | 2,094 | 1,707 |
| circular/ | H | 16-Oct-2021 | - | 130 | 116 |
| d/ | H | 16-Oct-2021 | - | 449 | 399 |
| e/ | H | 16-Oct-2021 | - | 1,060 | 1,029 |
| f/ | H | 16-Oct-2021 | - | 522 | 462 |
| g/ | H | 16-Oct-2021 | - | 1,005 | 827 |
| h/ | H | 16-Oct-2021 | - | 1,270 | 1,206 |
| i/ | H | 16-Oct-2021 | - | 197 | 177 |
| internal/ | H | 16-Oct-2021 | - | 202 | 169 |
| j/ | H | 16-Oct-2021 | - | 566 | 529 |
| k/ | H | 16-Oct-2021 | - | 99 | 90 |
| l/ | H | 16-Oct-2021 | - | 163 | 148 |
| m/ | H | 16-Oct-2021 | - | 1,051 | 967 |
| n/ | H | 16-Oct-2021 | - | 401 | 372 |
| o/ | H | 16-Oct-2021 | - | 500 | 450 |
| p/ | H | 16-Oct-2021 | - | 1,300 | 1,041 |
| q/ | H | 16-Oct-2021 | - | 131 | 121 |
| r/ | H | 16-Oct-2021 | - | 2,634 | 2,335 |
| s/ | H | 16-Oct-2021 | - | 1,706 | 1,586 |
| t/ | H | 16-Oct-2021 | - | 1,160 | 1,072 |
| testdata/ | H | 16-Oct-2021 | - | 35,908 | 34,662 |
| v/ | H | 16-Oct-2021 | - | 376 | 348 |
| w/ | H | 16-Oct-2021 | - | 34 | 29 |
| x/ | H | 16-Oct-2021 | - | 80 | 70 |
| y/ | H | 16-Oct-2021 | - | 131 | 103 |
| z/ | H | 16-Oct-2021 | - | 59 | 54 |
| README.md | H A D | 16-Oct-2021 | 1.9 KiB | 41 | 27 |
| lexer_benchmark_test.go | H A D | 16-Oct-2021 | 72.5 KiB | 2,473 | 1,677 |
| lexers.go | H A D | 16-Oct-2021 | 2.2 KiB | 61 | 39 |
| lexers_test.go | H A D | 16-Oct-2021 | 5.3 KiB | 192 | 152 |
README.md
1# Lexer tests
2
3The tests in this directory feed a known input `testdata/<name>.actual` into the parser for `<name>` and check
4that its output matches `<name>.exported`.
5
6It is also possible to perform several tests on a same parser `<name>`, by placing know inputs `*.actual` into a
7directory `testdata/<name>/`.
8
9## Running the tests
10
11Run the tests as normal:
12```go
13go test ./lexers
14```
15
16## Update existing tests
17When you add a new test data file (`*.actual`), you need to regenerate all tests. That's how Chroma creates the `*.expected` test file based on the corresponding lexer.
18
19To regenerate all tests, type in your terminal:
20
21```go
22RECORD=true go test ./lexers
23```
24
25This first sets the `RECORD` environment variable to `true`. Then it runs `go test` on the `./lexers` directory of the Chroma project.
26
27(That environment variable tells Chroma it needs to output test data. After running `go test ./lexers` you can remove or reset that variable.)
28
29### Windows users
30Windows users will find that the `RECORD=true go test ./lexers` command fails in both the standard command prompt terminal and in PowerShell.
31
32Instead we have to perform both steps separately:
33
34- Set the `RECORD` environment variable to `true`.
35 + In the regular command prompt window, the `set` command sets an environment variable for the current session: `set RECORD=true`. See [this page](https://superuser.com/questions/212150/how-to-set-env-variable-in-windows-cmd-line) for more.
36 + In PowerShell, you can use the `$env:RECORD = 'true'` command for that. See [this article](https://mcpmag.com/articles/2019/03/28/environment-variables-in-powershell.aspx) for more.
37 + You can also make a persistent environment variable by hand in the Windows computer settings. See [this article](https://www.computerhope.com/issues/ch000549.htm) for how.
38- When the environment variable is set, run `go tests ./lexers`.
39
40Chroma will now regenerate the test files and print its results to the console window.
41