#430 Changed directory structure of unit test report output #431
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
…ailed tests to "failed" and successful tests to "passed".
|
I added a comment to marklogic-community/marklogic-unit-test#46 - the exact tests that fail are printed out. This change would also deviate from how "gradle test" writes JUnit results out to a directory structure, so I don't want to go in that direction. |
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.
Changed the directory structure of unit test report output when running the mlUnitTest gradle task so that all failed tests are written to a "failed" directory within build/test-results/marklogic-unit-test, while all successful tests are written to a "passed" directory in the same location.
This should help solve the issue raised in marklogic-community/marklogic-unit-test#46 where it was pointed out that it wasn't possible to work out which tests have failed without looking through all the test reports.
I've also created a related pull request (marklogic-community/marklogic-unit-test#61) that deals with the other issue outlined in the above ticket that it's hard to read the test failure stack output.