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

coverage reporting #77

Open
Autoplectic opened this issue Feb 13, 2011 · 5 comments
Open

coverage reporting #77

Autoplectic opened this issue Feb 13, 2011 · 5 comments

Comments

@Autoplectic
Copy link

attest should have some way to report test coverage, probably using coverage.py. this is generally a very useful metric and so for attest to gain some real traction needs to support it.

@dag
Copy link
Owner

dag commented Feb 13, 2011

Doesn't it though work to simply do coverage run runtests.py?

If so I still should probably document it.

@dag
Copy link
Owner

dag commented May 8, 2011

With the new attest command it isn't obvious how to measure coverage. These should work:

coverage run -mattest
coverage run $(which attest)

These solutions should be documented as well.

@dqminh
Copy link

dqminh commented May 15, 2011

Running coverage run -mattest gives me this error: no such option -m. My attest version is 0.5.2.

@dag
Copy link
Owner

dag commented May 15, 2011

You are quite right, I noticed this too. The coverage docs claim -m is supposed to work but I get the same error. It does however work fine if you point it to a scriptfile that runs the tests.

@dag
Copy link
Owner

dag commented Jun 5, 2011

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

No branches or pull requests

3 participants