-
Notifications
You must be signed in to change notification settings - Fork 171
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 for aes encryption backend #422
base: master
Are you sure you want to change the base?
Add Tests for aes encryption backend #422
Conversation
…to feature/docker-updates
hangouts is dead and Google is the prime suspect
…34 image from archive
Fix Travis CI
Fix slack pip install version condition (missing comma)
tests for plugin module
…lack Html link converter slack
What do you think about including test for exceptions? The unfortunate part is that the code uses the catch-all exception so we don't have a very precise way to test for that. |
@Ashex I could probably assert that the exception message was written to the log. Would that satisfy the case? |
The aim would be to increase test coverage, I think checking that it was written to the log may not increase coverage of the code in question since we want to test for the exception itself being thrown. But do correct me if I'm wrong. |
I meant if I force an exception by breaking it in the test, and then asserting the log was written it should execute the code. |
Okay understood, I think that would be a worthwhile test! |
This adds two tests:
I would like to fix the pycrypto vulnerability as mentioned in #385
So I figured the first step is to add test coverage.