The tests in this directory feed a known input testdata/<name>.actual
into the parser for <name>
and check
that its output matches <name>.exported
.
Run the tests as normal:
go test ./lexers
When 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.
To regenerate all tests, type in your terminal:
RECORD=true go test ./lexers
This first sets the RECORD
environment variable to true
. Then it runs go test
on the ./lexers
directory of the Chroma project.
(That environment variable tells Chroma it needs to output test data. After running go test ./lexers
you can remove or reset that variable.)
Windows users will find that the RECORD=true go test ./lexers
command fails in both the standard command prompt terminal and in PowerShell.
Instead we have to perform both steps separately:
RECORD
environment variable to true
.
set
command sets an environment variable for the current session: set RECORD=true
. See this page for more.$env:RECORD = 'true'
command for that. See this article for more.go tests ./lexers
.Chroma will now regenerate the test files and print its results to the console window.