diff options
| author | Aleksey Kladov <aleksey.kladov@gmail.com> | 2020-06-15 11:02:17 +0200 |
|---|---|---|
| committer | Aleksey Kladov <aleksey.kladov@gmail.com> | 2020-06-15 11:02:17 +0200 |
| commit | b5c4f2faa2a39bad9af35e7d90e9ed6151a6a0d5 (patch) | |
| tree | ded375c0f374b85f7e65f7826a1c1071d6222e81 /docs/dev | |
| parent | d739731830d5ad289f1bb779ed58cc1ea3cb5734 (diff) | |
| download | rust-b5c4f2faa2a39bad9af35e7d90e9ed6151a6a0d5.tar.gz rust-b5c4f2faa2a39bad9af35e7d90e9ed6151a6a0d5.zip | |
Update parser tests with env var
Diffstat (limited to 'docs/dev')
| -rw-r--r-- | docs/dev/README.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md index 2e4a459988f..4cb5dfaa053 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md @@ -342,6 +342,12 @@ There are two kinds of tests: The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for. If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test. +To update test data, run with `UPDATE_EXPECTATIONS` variable: + +```bash +env UPDATE_EXPECTATIONS=1 cargo qt +``` + # Logging Logging is done by both rust-analyzer and VS Code, so it might be tricky to |
