Part of Android Studio Integration: JUnit XML generation #4356
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
irodotos7
force-pushed
the
android/xml-test-report
branch
from
ce871a0 to
589bcc6
Compare
vaslabs
force-pushed
the
android/xml-test-report
branch
2 times, most recently
from
433f36d to
5c80f04
Compare
vaslabs
force-pushed
the
android/xml-test-report
branch
from
0c32195 to
602df0b
Compare
|
Looks good to me, happy to merge it if you're done |
Feel free to merge it. Thank you! |
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.
Provided in this PR
After running Instrumental tests the XML will automatically created in the out/app/it/testTask.dest/ directory
JUnit XML validation
Using this online tool link we can validate that the XML is correct