diff options
author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-07-01 11:31:39 +0100 |
---|---|---|
committer | GitHub <[email protected]> | 2020-07-01 11:31:39 +0100 |
commit | 7d82152b21579df144b4a5272e699e24cafb5b97 (patch) | |
tree | 78b54055f2f5394ce4b75bbaf6f97bad466710ae /docs | |
parent | a9db3d53a0997010f8d3f9c9b14636bef3754f8b (diff) | |
parent | 991850bc3c2ff34fe8b3e63815067307d8d90db6 (diff) |
Merge #5163
5163: Refactor parser tests a bit r=matklad a=matklad
bors r+
🤖
Co-authored-by: Aleksey Kladov <[email protected]>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/dev/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md index f1139d2f4..f87462400 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md | |||
@@ -361,10 +361,10 @@ There are two kinds of tests: | |||
361 | 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. | 361 | 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. |
362 | 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. | 362 | 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. |
363 | 363 | ||
364 | To update test data, run with `UPDATE_EXPECTATIONS` variable: | 364 | To update test data, run with `UPDATE_EXPECT` variable: |
365 | 365 | ||
366 | ```bash | 366 | ```bash |
367 | env UPDATE_EXPECTATIONS=1 cargo qt | 367 | env UPDATE_EXPECT=1 cargo qt |
368 | ``` | 368 | ``` |
369 | 369 | ||
370 | After adding a new inline test you need to run `cargo xtest codegen` and also update the test data as described above. | 370 | After adding a new inline test you need to run `cargo xtest codegen` and also update the test data as described above. |