Replace XCResultKit in order to support Swift testing fully#64
Merged
Conversation
a7ex
requested review from
Brett-Best,
DanielBarberaDimoftache-TomTom,
MatthewTHFisher,
alexdeem,
darrarski,
grant-mccarriagher,
hisaac,
jszumski,
liuyunclouder,
luispadron,
maxwell-legrand and
nkokhelox
Collaborator
|
I tested this out and it generates test results and code coverage fine for the project I'm using it for. Thanks for getting off of the legacy command flag! |
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
2 participants
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.
Major overhaul of the tool.
It doesn't use XCResultKit anymore, as that made me stuck to deprecated xcresulttool output. In order to display e.g. parametrized tests, xcresultparser now interfaces directly with xcresulttool.
Major changes, please test your use cases.