-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Can't get code coverage to work.... #1731
Comments
Hi, this module is very old and it looks like nobody tested it for a decade. Does |
Please excuse my ignorance but how would I use that with cherrypy?
…On Thu, Aug 30, 2018 at 6:04 AM Sviatoslav Sydorenko < ***@***.***> wrote:
Hi, this module is very old and it looks like nobody tested it for a
decade. Does pytest-cov work for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1731 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAu8f6K_4m19JxH52qfk7au37QupFzLIks5uV7iVgaJpZM4WIqXR>
.
|
Do you use |
I don't now, but I am willing to try it. anything special I have to do to
get it to work with CherryPy?
…On Mon, Sep 3, 2018 at 11:23 AM Sviatoslav Sydorenko < ***@***.***> wrote:
Do you use pytest for testing? It should be able to pick up cov plugin if
you pip install pytest-cov
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1731 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAu8f6-ijxvygEwBZWQhQq5UYzdQ70Dbks5uXUmAgaJpZM4WIqXR>
.
|
I don't yet know, but it's used in CI while testing CherryPy itself. Tell us about your experience once you try :) |
This might result in a good enhancement of documentation. |
cc @jaraco |
I don't know anything about covercp. That module clearly has bugs and it's not clear how to use it. I welcome PRs to improve that module and the documentation around how to use it. Whoever works on that will have to spend some time troubleshooting and establishing an understanding of that module and it's purpose(s). |
Got coverage to work with pytest and --cov flag
Would you like me to write up some simple documentation showing how to do
It with one of the tutorial projects? Then my suggestion would be to
remove covercp from the project.
…On Mon, Sep 3, 2018 at 11:56 AM Jason R. Coombs ***@***.***> wrote:
I don't know anything about covercp. That module clearly has bugs and it's
not clear how to use it. I welcome PRs to improve that module and the
documentation around how to use it. Whoever works on that will have to
spend some time troubleshooting and establishing an understanding of that
module and it's purpose(s).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1731 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAu8f6zVibQmqSAmBWjySiq7lm-DncJ6ks5uXVE0gaJpZM4WIqXR>
.
|
@alan412 that would be lovely! The docs source is here: https://github.com/cherrypy/cherrypy/tree/master/docs I believe that this module facilitated coverage in times of cherrypy/cherrypy/lib/covercp.py Line 11 in 2fc78dc
|
Do you want to request a feature or report a bug?
I don't know if it is a bug or just my not knowing what I am doing.
What is the current behavior?
When I try to execute covercp.py, I get the following:
If I comment out lines 377 and 378 then it will start up, but I get the following on the left hand side:
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
What is the expected behavior?
I would really like (and think would be great to have in the documentation) an example using code coverage of one of the tutorial projects. I suspect I am just doing something not very smart.
What is the motivation / use case for changing the behavior?
I would like to use code coverage to make sure my tests are covering enough of the project for a release.
Please tell us about your environment:
-Python 3.6.1
The text was updated successfully, but these errors were encountered: