This repository has been archived by the owner on May 13, 2022. It is now read-only.
Add errors/failures to JUnit report #187
Merged
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
Adds a failure and error tag to JUnit output so that Bamboo (and presumably other CI systems) will parse the file correctly.
We were running into an issue where Bamboo was treating each test as different from last time it was ran because it had a different (uniquely generated) class name based on the test_set. This meant that a test suite that has 3 failures would show as 3 *new* failures each time it's run rather than 3 *existing* failures.
luciano-renzi
approved these changes
Mar 27, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds a failure and error tag to JUnit output so that Bamboo (and other CI systems) will parse the file correctly.
This should address issue #180