Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Separate code coverage reports for unit tests and integration tests #1018

Open
rhyolight opened this issue Jun 16, 2014 · 2 comments
Open

Separate code coverage reports for unit tests and integration tests #1018

rhyolight opened this issue Jun 16, 2014 · 2 comments
Assignees
@rhyolight
Labels
priority:4 triage type:build type:cleanup type:tests

Comments

@rhyolight
Copy link
Member

Currently, only integration tests are reported to coveralls.io. Ideally, we'd have these tests separated out so they could both be reported separately.
@rhyolight rhyolight changed the title Code coverage reports for unit separate from integration tests Separate code coverage reports for unit tests and integration tests Jun 16, 2014
@rhyolight rhyolight mentioned this issue Jun 16, 2014
Merged
@rhyolight
Copy link
Member Author

Partially completed by #1019, but that only reports on unit tests. I still need to figure out how to report for both unit and integration tests from within the same build job.

@rhyolight rhyolight added this to the Sprint 24 milestone Jun 18, 2014
@rhyolight rhyolight self-assigned this Jun 18, 2014
@rhyolight rhyolight removed this from the Sprint 24 milestone Jun 20, 2014
@rhyolight rhyolight added the P3 label Aug 20, 2014
@rhyolight rhyolight added this to the Testing milestone Sep 19, 2014
@rhyolight
Copy link
Member Author

Depends on z4r/python-coveralls#23.

@rhyolight rhyolight modified the milestone: Testing Oct 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rhyolight rhyolight

Labels
priority:4 triage type:build type:cleanup type:tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rhyolight