We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Because it typically indicates something is seriously wrong, and you just want to see the errors right away.
The text was updated successfully, but these errors were encountered:
@krlmlr how do you feel about this being the default behaviour? i.e. if there are > getOption("testthat.summary.max_reports", 15L) we terminate reporter early?
> getOption("testthat.summary.max_reports", 15L)
Sorry, something went wrong.
Now included in #502.
This is mildly tricky as we need a new subclass of stop that will immediately terminate execution of the entire test suite, and not get captured like usual errors.
Could you please check if de82b5b would also work?
I wrote my comment on the plane a couple of days ago when I didn't have internet access and only just submitted it. I think your approach is fine.
Offline comments? Intriguing. (Or was it just an open browser tab? ;-) )
Open browser tab ;)
Successfully merging a pull request may close this issue.