-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
test_runner: print failed tests with dot reporter #51769
Comments
Hi! I am interested in working on this issue. I could reproduce the scenario and can see what you mean. I would like to understand the requirements. Is the dot reporter required to print the names of the tests that failed? |
Yes, it seems like that is what @mcollina was going for, but I could be wrong. |
It should report the name of failed tests identically to the spec reporter. |
Looks good to start, if you submit a PR we can review it (and address any errors with it) |
Add failed test names and execution times to dot reporter output, improving issue identification without verbose reporting. Fixes: nodejs#51769
I've noticed suggestions to include stack traces in the dot reporter's output. Would adding detailed stack traces make it too similar to the spec reporter? |
the proposal is to do this only for failed tests |
test_runner: dot reporter displays failed tests Fixes: nodejs#51769 test_runner: fixes for dot reporter displaying failed test names test_runner: fixed conventions for dot reporter test_runner: added symbols to utils for reusability test_runner: squashed utility function changes for failed test test_runner: dot reporter displays failed test name and trace test_runner: added a utility function to print failed test test_runner: handled global variable, updated snapshots test_runner: added space after Failed tests message
I don't think that the dot reporter is really useful, because in case of failures it does not print the failed tests. Could we make it print the failed tests?
The text was updated successfully, but these errors were encountered: