Support for RSpec Junit reporting #78
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds support for Junit reporting. It seems the current design of turbo tests is not able to work with RSpec Junit, no matter what args or configuration I try. This is important for CircleCI. I work on a couple projects using
parallel_testsin Circle, but it would be nice to have consolidated log output with failures listed together, as turbo_tests does. However, switching to turbo_tests removes the failing tests from theTeststab in Circle (see working example below). Getting RSpec Junit to work makes it possible to use turbo tests in Circle and still extract the failures into that tab