Skip to content

Commit 4e11c96

Browse files
committed
CheckReporter runs in parallel; DebugReporter runs sequentially
1 parent a5716a1 commit 4e11c96

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

vignettes/parallel.Rmd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,10 +111,10 @@ The other built-in reporters all support parallel tests, with some subtle differ
111111
`ProgressReporter` does not update its display until a test file is complete.
112112

113113
- The standard output and standard error, i.e. `print()`, `cat()`, `message()`, etc. output from the test files are lost currently.
114-
If you want to use `cat()` or `message()` for print-debugging test cases, then the best is to temporarily run tests sequentially, by changing the `Config` entry in `DESCRIPTION` or selecting a non-parallel reporter, e.g. the `CheckReporter`:
114+
If you want to use `cat()` or `message()` for print-debugging test cases, then the best is to temporarily run tests sequentially, by changing the `Config` entry in `DESCRIPTION` or selecting a non-parallel reporter, e.g. the `DebugReporter`:
115115

116116
``` r
117-
devtools::test(filter = "badtest", reporter = "check")
117+
devtools::test(filter = "badtest", reporter = "debug")
118118
```
119119

120120
### Writing parallel reporters

0 commit comments

Comments
 (0)