Print failures from test reports #49
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to show the exceptions in (hopefully) all cases, this commit simply prints 100+ lines of relevant sections of HTML to the console. For `TestEngine with ID 'junit-jupiter' failed to discover tests` this should be sufficient. Many online posts suggestions to configure the `testLogging` block do not result in displaying an exception when Jupiter fails at running a test. It is also surprising to find no `stdout` or `stderr` report options out of the box. I guess when Gradle and Jupiter were coming of age, Jenkins was the CI/CD system de jour and made it trivial to see these reports. Issue #48: Show test failure output in job
slifty
approved these changes
Jun 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to show the exceptions in (hopefully) all cases, this commit simply prints 100+ lines of relevant sections of HTML to the console. For
TestEngine with ID 'junit-jupiter' failed to discover teststhis should be sufficient.Many online posts suggestions to configure the
testLoggingblock do not result in displaying an exception when Jupiter fails at running a test. It is also surprising to find nostdoutorstderrreport options out of the box. I guess when Gradle and Jupiter were coming of age, Jenkins was the CI/CD system de jour and made it trivial to see these reports.Issue #48: Show test failure output in job