JUnitReportReporter should capture the test case output at the test c… #2876
Conversation
This file contains 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
krmahadevan
approved these changes
Feb 6, 2023
|
@juherr - Please help check and share your inputs so that we can wrap this PR. |
|
@juherr - Gentle reminder on this. |
juherr
approved these changes
Feb 24, 2023
|
|
||
| // Add the full reporter output once as a child system-out element of testsuite. | ||
| List<String> output = Reporter.getOutput(); | ||
| if ((!output.isEmpty())) { |
There was a problem hiding this comment.
I will take care of fixing this. Going ahead with merging this PR @juherr
1 task
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.
Fixes #2875 - JUnitReportReporter should capture the test case output at the test case level
Did you remember to?
CHANGES.txt./gradlew autostyleApplyWe encourage pull requests that:
If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the
TestNG-dev before you spend time working on it.
Note: For more information on contribution guidelines please make sure you refer our Contributing section for detailed set of steps.