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
| `FILTER_CRATE` | `string` | Only include results from the given crate. In the GUI, this is the "Results in <kbd>crate</kbd>" drop-down menu.
378
377
| `EXPECTED` | `[ResultsTable]\|ResultsTable` | List of tests to run, specifying what the hypothetical user types into the search box and sees in the tabs
379
378
| `PARSED` | `[ParsedQuery]\|ParsedQuery` | List of parser tests to run, without running an actual search
380
379
380
+
`FILTER_CRATE` can be left out (equivalent to searching "all crates"), but you
381
+
have to specify `EXPECTED` or `PARSED`.
382
+
381
383
Additionally, the following magic comments are supported.
382
384
Put them on their own line, without indenting.
383
385
@@ -390,12 +392,9 @@ Put them on their own line, without indenting.
390
392
to minor scoring changes.
391
393
*`// should-fail`: Used to write negative tests.
392
394
393
-
Standard library tests probably shouldn't specify any of these (we want the
394
-
libs team to be able to add new stuff without causing our tests to fail), but
395
-
standalone tests will often want `// exact-check`.
396
-
397
-
`FILTER_CRATE` can be left out (equivalent to searching "all crates"), but you
398
-
have to specify `EXPECTED` or `PARSED`.
395
+
Standard library tests usually shouldn't specify `// exact-check`, since we
396
+
want the libs team to be able to add new items without causing unrelated
397
+
tests to fail, but standalone tests will use it more often.
399
398
400
399
The `ResultsTable` and `ParsedQuery` types are specified in
0 commit comments