You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dev/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -361,10 +361,10 @@ There are two kinds of tests:
361
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
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
366
```bash
367
-
env UPDATE_EXPECTATIONS=1 cargo qt
367
+
env UPDATE_EXPECT=1 cargo qt
368
368
```
369
369
370
370
After adding a new inline test you need to run `cargo xtest codegen` and also update the test data as described above.
0 commit comments