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

Expand test coverage #7

Closed
dstufft opened this issue Oct 4, 2013 · 6 comments
Closed

Expand test coverage #7

dstufft opened this issue Oct 4, 2013 · 6 comments
Labels
bug testing Test frameworks, tests, etc.

Comments

@dstufft
Copy link
Member

dstufft commented Oct 4, 2013

No description provided.

@brainwane brainwane added the testing Test frameworks, tests, etc. label Feb 28, 2018
@brainwane brainwane changed the title Test Everything Expand test coverage Mar 1, 2018
@brainwane
Copy link
Contributor

Trying to list out what "test everything" would mean:

Codecov says we're at 67.42% code coverage. Out of 574 tracked lines, we hit 387, partially hit 25, and miss 162. upload.py, for instance, has substantial untested code.

I think we don't have any doctests.

We have some tests running via Travis CI.

We could add PEP 484 annotations (#231).

@dstufft
Copy link
Member Author

dstufft commented Mar 1, 2018

100% coverage or bust is my motto :P

@deveshks
Copy link
Contributor

Hi @bhrutledge , @dstufft

Is this something I can take a stab at?

I started with twine/utils.py and was able to get 99% test coverage with it, from 96% . I will be happy to create a PR for the same, and then increase coverage for more files, with one file per PR.

Before

Name                           Stmts   Miss Branch BrPart  Cover   Missing
twine/utils.py                  98      4     40      2    96%   111->112, 112, 118-126, 172->177
------------------------------------------------------------------------
TOTAL                          829     70    241     35    88%

After

Name                           Stmts   Miss Branch BrPart  Cover   Missing
twine/utils.py                  98      0     40      1    99%   172->177
------------------------------------------------------------------------
TOTAL                           829     66    241     34    89%


@bhrutledge
Copy link
Contributor

@deveshks Yes please! This is how I got started contributing to Twine, at last year's PyCon sprints: #458.

@deveshks
Copy link
Contributor

@deveshks Yes please! This is how I got started contributing to Twine, at last year's PyCon sprints: #458.

Thanks, I have submitted the first PR towards the effort

@jaraco
Copy link
Member

jaraco commented Jun 20, 2020

Coverage is now at 93%. That's satisfactory. Nicer would be to get to 100%, so ongoing contribution is welcomed.

@jaraco jaraco closed this as completed Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug testing Test frameworks, tests, etc.
Projects
None yet
Development

No branches or pull requests

5 participants