1
0
mirror of https://github.com/alecthomas/chroma.git synced 2025-03-25 21:39:02 +02:00
Jelle Hulter c56819b5da
Fixed OpenEdgeABL String literals (#652)
When OpenEdge ABL runs on Windows, the tilde is used as an escape character instead of a backslash as in most common programming languages. On UNIX platforms, the backslash is also an escape character. But because we cannot know the running platform, it seems better to only use the tilde as a backslash character. (source: https://knowledgebase.progress.com/articles/Article/P27229)
2022-10-05 17:15:25 -07:00
..
2022-10-05 17:12:32 -07:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-06-23 10:53:42 +10:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-06-27 01:18:15 -07:00
2022-07-13 14:26:31 -07:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-07-20 14:20:15 -07:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2021-05-07 08:42:53 +10:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00
2022-06-04 06:00:44 -07:00
2022-01-27 15:22:00 +11:00
2022-01-27 15:22:00 +11:00

Lexer tests

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.

It is also possible to perform several tests on a same parser <name>, by placing know inputs *.actual into a directory testdata/<name>/.

Running the tests

Run the tests as normal:

go test ./lexers

Update existing tests

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

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:

  • Set the RECORD environment variable to true.
    • In the regular command prompt window, the set command sets an environment variable for the current session: set RECORD=true. See this page for more.
    • In PowerShell, you can use the $env:RECORD = 'true' command for that. See this article for more.
    • You can also make a persistent environment variable by hand in the Windows computer settings. See this article for how.
  • When the environment variable is set, run go tests ./lexers.

Chroma will now regenerate the test files and print its results to the console window.