New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code coverage #16
Code coverage #16
Conversation
87393c1
to
5b6860a
Compare
xcpretty is used to make xcodebuild test logs more readable
b0b702c
to
dc3c7e8
Compare
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
- run: | ||
name: Generate Coverage Reports | ||
command: | | ||
rake codecov:ios |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 1:
merged with 53dfdb4 |
Code coverage implementation on CircleCI along with pretty output with xcpretty during testing has been implemented.