diff options
-rw-r--r-- | docs/dev/architecture.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/dev/architecture.md b/docs/dev/architecture.md index 9e9651801..680910f38 100644 --- a/docs/dev/architecture.md +++ b/docs/dev/architecture.md | |||
@@ -83,11 +83,11 @@ Rust syntax tree structure and parser. See | |||
83 | visiting the nodes (this is double plus cool, if you understand how | 83 | visiting the nodes (this is double plus cool, if you understand how |
84 | `Visitor` works, you understand the design of syntax trees). | 84 | `Visitor` works, you understand the design of syntax trees). |
85 | 85 | ||
86 | Tests for ra_syntax are mostly data-driven: `tests/data/parser` contains a bunch of `.rs` | 86 | Tests for ra_syntax are mostly data-driven: `test_data/parser` contains subdirectories with a bunch of `.rs` |
87 | (test vectors) and `.txt` files with corresponding syntax trees. During testing, we check | 87 | (test vectors) and `.txt` files with corresponding syntax trees. During testing, we check |
88 | `.rs` against `.txt`. If the `.txt` file is missing, it is created (this is how you update | 88 | `.rs` against `.txt`. If the `.txt` file is missing, it is created (this is how you update |
89 | tests). Additionally, running `cargo gen-tests` will walk the grammar module and collect | 89 | tests). Additionally, running `cargo gen-tests` will walk the grammar module and collect |
90 | all `//test test_name` comments into files inside `tests/data` directory. | 90 | all `// test test_name` comments into files inside `test_data/parser/inline` directory. |
91 | 91 | ||
92 | See [#93](https://github.com/rust-analyzer/rust-analyzer/pull/93) for an example PR which | 92 | See [#93](https://github.com/rust-analyzer/rust-analyzer/pull/93) for an example PR which |
93 | fixes a bug in the grammar. | 93 | fixes a bug in the grammar. |