-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add options to print stack trace / stdout / stderr on error or failure #39
Conversation
Hey! Really nice PR, thanks for that! I didn't know it was possible to get params from the XML like that! :) I will merge to the |
If I can help, let me know. This plugin is really useful, we've got integration tests that produce huge amounts of logging output. The log files from the CI run are now only a few MB instead of several dozen MB : ) |
* Fixed #30 - Upgrade to maven-surefire-plugin:3.0.0-M8 (#31) * Fixed #32 - Using JUnit Jupiter BOM 5.9.2 (#33) * Fixed #34 - Using mockito-bom 4.11.0 (#35) * Add options to print stack trace / stdout / stderr on error or failure (#39) * Update README, pom.xml and make it Java 8 compatible (#41) --------- Co-authored-by: Karl Heinz Marbaise <[email protected]> Co-authored-by: Andre Wachsmuth <[email protected]> Co-authored-by: Andre Wachsmuth <[email protected]>
* Fixed #30 - Upgrade to maven-surefire-plugin:3.0.0-M8 (#31) * Fixed #32 - Using JUnit Jupiter BOM 5.9.2 (#33) * Fixed #34 - Using mockito-bom 4.11.0 (#35) * Add options to print stack trace / stdout / stderr on error or failure (#39) * Update README, pom.xml and make it Java 8 compatible (#41) --------- Co-authored-by: Karl Heinz Marbaise <[email protected]> Co-authored-by: Andre Wachsmuth <[email protected]> Co-authored-by: Andre Wachsmuth <[email protected]>
* Fixed #30 - Upgrade to maven-surefire-plugin:3.0.0-M8 (#31) * Fixed #32 - Using JUnit Jupiter BOM 5.9.2 (#33) * Fixed #34 - Using mockito-bom 4.11.0 (#35) * Add options to print stack trace / stdout / stderr on error or failure (#39) * Update README, pom.xml and make it Java 8 compatible (#41) --------- Co-authored-by: Karl Heinz Marbaise <[email protected]> Co-authored-by: Andre Wachsmuth <[email protected]> Co-authored-by: Andre Wachsmuth <[email protected]>
I have just deployed the new version |
I just found this extension and it is great! Makes test output much more readable. One thing I did miss, however, is the ability to see console output and stack traces when a test fails. This commit
<theme>ASCII</code>
or<theme>UNICODE</theme>
option and deprecatesJUnit5StatelessTestsetInfoTreeReporterUnicode
in favor of that option. If we have multiple options, the theme might as well be an option as well.From the readme:
The options all default to
false
to preserve the current behavior. Although I think it would also help to print details for errors and failures by default.The resulting output looks like this: