diff options
author | Aleksey Kladov <[email protected]> | 2020-06-15 10:02:17 +0100 |
---|---|---|
committer | Aleksey Kladov <[email protected]> | 2020-06-15 10:02:17 +0100 |
commit | b5c4f2faa2a39bad9af35e7d90e9ed6151a6a0d5 (patch) | |
tree | ded375c0f374b85f7e65f7826a1c1071d6222e81 /docs | |
parent | d739731830d5ad289f1bb779ed58cc1ea3cb5734 (diff) |
Update parser tests with env var
Diffstat (limited to 'docs')
-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 2e4a45998..4cb5dfaa0 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md | |||
@@ -342,6 +342,12 @@ There are two kinds of tests: | |||
342 | 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. | 342 | 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. |
343 | 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. | 343 | 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. |
344 | 344 | ||
345 | To update test data, run with `UPDATE_EXPECTATIONS` variable: | ||
346 | |||
347 | ```bash | ||
348 | env UPDATE_EXPECTATIONS=1 cargo qt | ||
349 | ``` | ||
350 | |||
345 | # Logging | 351 | # Logging |
346 | 352 | ||
347 | Logging is done by both rust-analyzer and VS Code, so it might be tricky to | 353 | Logging is done by both rust-analyzer and VS Code, so it might be tricky to |