coverage reporting #77

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

Comments

Projects
None yet
3 participants
@Autoplectic

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

This comment has been minimized.

Show comment
Hide comment
@dag

dag Feb 13, 2011

Owner

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

If so I still should probably document it.

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

This comment has been minimized.

Show comment
Hide comment
@dag

dag May 8, 2011

Owner

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.

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

This comment has been minimized.

Show comment
Hide comment
@dqminh

dqminh May 15, 2011

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

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

This comment has been minimized.

Show comment
Hide comment
@dag

dag May 15, 2011

Owner

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.

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.

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