aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJacek Generowicz <[email protected]>2020-06-10 19:32:29 +0100
committerJacek Generowicz <[email protected]>2020-06-10 19:32:29 +0100
commitf280407d7350c2abc4cc35389d389acdc5d93e28 (patch)
treee993542f8cbcb2036b9c5791f37c206ee24b7e0f /docs
parent96309ba4a1bbbffd1c03f50a21bb68526550b925 (diff)
Fix parser test directory name in dev docs
Diffstat (limited to 'docs')
-rw-r--r--docs/dev/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index cf93135ee..ef5ffbf59 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -308,7 +308,7 @@ The results are 100% Rust specific though.
308Test for parser (`ra_parser`) live in `ra_syntax` crate (see `test_data` direcotory). 308Test for parser (`ra_parser`) live in `ra_syntax` crate (see `test_data` direcotory).
309There are two kinds of tests: 309There are two kinds of tests:
310 310
311* Manually written test cases in `parser/ok` and `parser/error` 311* Manually written test cases in `parser/ok` and `parser/err`
312* "Inline" tests in `parser/inline` (these are generated) from comments in `ra_parser` crate. 312* "Inline" tests in `parser/inline` (these are generated) from comments in `ra_parser` crate.
313 313
314The 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. 314The 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.