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.

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

update tests to check coverage of py3 code instead of setting "no cover" #1470

Closed
mmerickel opened this issue Nov 21, 2014 · 2 comments · Fixed by #1471
Closed

update tests to check coverage of py3 code instead of setting "no cover" #1470

mmerickel opened this issue Nov 21, 2014 · 2 comments · Fixed by #1471

Comments

@mmerickel
Copy link
Member

It's possible to run coverage on multiple targets and combine their results into a final analysis. We should try to do this to properly test coverage on py2 and py3.

http://nedbatchelder.com/code/coverage/cmd.html#cmd-combining
http://stackoverflow.com/questions/19274492/how-calculate-the-global-coverage

Related: #979

@gcarothers
Copy link

How does this play with tox setup on travis? Doesn't each one of the builds get executed in it's own sandbox? Or is this only for local execution?

@gcarothers
Copy link

Heh, I see you in fact already ran into this in 11ba5a5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants