-
Notifications
You must be signed in to change notification settings - Fork 22
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
Improve test coverage #48
Comments
perrette
pushed a commit
that referenced
this issue
Apr 25, 2023
perrette
pushed a commit
that referenced
this issue
Apr 25, 2023
- dry-run as part of add bib - test_biblio to tests specific Biblio methods (here __eq__) - papers uninstall in teaddown => needed to fix one test with --relative-path !
@boyanpenkov I think we are now in a better shape to work on the tests (split by thematics, coverage works).
|
OK, no problem; I'll keep this in mind. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We now have about 60% test coverage (test coverage issues were fixed in #44).
As a first objective, we should aim for 100% test coverage for
__main__.py
, i.e. that every sub-command and if/then/else branching is executed at least once. That way we can be sure that namespace, import and other syntax errors ring the bell. From there, we can start thinking about semantic, i.e. thinking about simple and intricate cases where we expect a meaningful result.The coverage reporting includes a missing lines section that is more informative:
The text was updated successfully, but these errors were encountered: