-
Notifications
You must be signed in to change notification settings - Fork 7
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
use TestCase.assertRaises with a specific exception type/message instead of catching/printing all Exceptions |
Split existing tests into smaller units |
Updating with WIP information from #83 Notable uncovered areasIn addition to numerous exceptions and minor branches that are not covered (i.e. raising an exception if a file that should always be present is missing), the following areas have functional code that is currently untested but could be:
DFTB tests don't run, as
The following files have no coverage, and are not called anywhere else in the codebase. Could write tests for them, but is it worth it for code that is never used? May have value as library functions but it's not obvious to me if they do. Following discussion with @leandro-liborio will keep the following:
And remove the following:
|
Broad improvements needed to coverage:
Specific improvements to existing tests:
The text was updated successfully, but these errors were encountered: