-
Notifications
You must be signed in to change notification settings - Fork 154
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
Add tests #16
Comments
For now, #36 fixes the failing travis build. I replaces |
I'm interested in adding some tests. We can use the official testing provided by Click. Should we place the tests inside the modules or a separate directory? |
@systemplado that's cool! 😄 We should use that. We should place the tests in a different directory, since it's not a module. |
As suggested by @systemplado, I have started writing tests for |
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
refs #16 increase coverage for diary module
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
refs #16 clean up unused modules, increase coverage
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
Signed-off-by: Man Parvesh Singh Randhawa <[email protected]>
I think it is okay to believe that the test coverage is fine for the project. However, I think it still needs improvement, so this will be continued in #71 and I will close this issue |
Description:
Add automated tests to the project. Currently, the Travis build simply runs pytest, but since there are no tests, it passes.
This task will take a considerable effort.
Checklist:
The text was updated successfully, but these errors were encountered: