Code coverage #16
Closed
Code coverage #16
Conversation
mkchoi212
force-pushed the
mkchoi212:code-cov
branch
4 times, most recently
from
87393c1
to
5b6860a
xcpretty is used to make xcodebuild test logs more readable
mkchoi212
force-pushed the
mkchoi212:code-cov
branch
3 times, most recently
from
b0b702c
to
dc3c7e8
|
Gave up on slather because it had some major bugs that need fixing. And Caro brought up a good point about trying to limit the number of dependencies. So instead of slather, Apple's xccov is being used. The generated report is rather plain but as services like codecov.io start adopting the new format, I think we should look into using their services for making the reports look more comprehensible. Here's a dummy CircleCI build with some test code in it. |
Closed
|
looks good to me |
| - run: | ||
| name: Generate Coverage Reports | ||
| command: | | ||
| rake codecov:ios |
carolanitz
Jun 6, 2018
Member
👍 1:
|
merged with 53dfdb4 |
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.
Code coverage implementation on CircleCI along with pretty output with xcpretty during testing has been implemented.