-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
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? Sign in to your account
Summary of skipped tests #343
Conversation
I like the idea, but I think the output could be more compact, e.g.:
|
This might also be a good template for how to handle warnings (#310) |
Implemented more compact output. |
8307196
to
6369008
Compare
Related: #310. |
@hadley: How to include the context in the output, if at all? (Same question for error and warning output.) |
Print file + line rather than context: #352 |
There are two possible file + line locations to report: The test that failed/warned/skipped, and the actual code that causes the error/warning/skip. The former should be always available, even if the latter is not (#352 (comment)). |
I think we should try for the actual line of code, and fall back to the test. |
This is complete "as is", file + line information should be handled separately (#352). |
Shows skipped tests, but only if there are no failures. Example:
Will improve the coding once we agree on the concept.
Fixes #234.
CC @HarlanH @kenahoo-windlogics
Fixes #349 (=includes it).