From afa94d4f37b9a0a1e723edffcc79c3d48799bad1 Mon Sep 17 00:00:00 2001 From: Aleksey Kladov Date: Thu, 9 Aug 2018 17:44:40 +0300 Subject: fn_item -> function --- docs/TESTS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/TESTS.md') diff --git a/docs/TESTS.md b/docs/TESTS.md index db06dbebc..a9d32d1d4 100644 --- a/docs/TESTS.md +++ b/docs/TESTS.md @@ -24,20 +24,20 @@ recovery and it is totally ok for a parser to not implement any error recovery at all. However, for libsyntax2.0 we do care about error recovery, and we do care about precise and useful error messages. -There are also so-called "inline tests". They appear as the comments +There are also so-called "inline tests". They appear as the comments with a `test` header in the source code, like this: ```rust // test fn_basic // fn foo() {} -fn fn_item(p: &mut Parser) { +fn function(p: &mut Parser) { // ... } -``` +``` -You can run `cargo collect-tests` command to collect all inline tests +You can run `cargo collect-tests` command to collect all inline tests into `tests/data/inline` directory. The main advantage of inline tests -is that they help to illustrate what the relevant code is doing. +is that they help to illustrate what the relevant code is doing. Contribution opportunity: design and implement testing infrastructure -- cgit v1.2.3