Adding support for Casper JUnit output #51
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
We are using the standard casper xunit output but it isn’t very nice when you use the standard JUnit parser for res. This creates much nicer representation. JUnit gives you one ‘Suites’ but we want to use the files the tests have come from as the ‘Suites’. So we do this using the packagenames function to find unique packagenames on the individual suites and create a list of them. JUnit also gives you a system-out in every test suite. We’re just checking for testcases inside the suites so we don’t get these anymore. We have also restricted the length of the names of testsuties to ensure they fit into databases. I think we may want to improve on this in the future. This work was done very much in conjunction with: https://github.com/Asimk21
jrmhaig
added a commit
that referenced
this pull request
Jan 4, 2016
Adding support for Casper JUnit output
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.
This is to add support for Casper JUnit ouput.
We are using the standard casper xunit output but it isn’t very nice when you use the standard JUnit parser for res.
This creates much nicer representation.
JUnit gives you one ‘Suites’ but we want to use the files the tests have come from as the ‘Suites’. So we do this using the packagenames function to find unique packagenames on the individual suites and
create a list of them.
JUnit also gives you a system-out in every test suite. We’re just checking for testcases inside the suites so we don’t get these anymore.
We have also restricted the length of the names of testsuties to ensure they fit into databases. I think we may want to improve on this in the future.
This work was done very much in conjunction with:
https://github.com/Asimk21