-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Increase test coverage #187
Labels
Comments
@glaslos Can you please describe the test to be added with an example. |
You can find examples of tests here:
https://github.com/mushorg/snare/tree/master/snare/tests
First step should be finding out where we lack coverage. Maybe use a
service like coverall?
|
I am working on this issue I will update soon |
This was referenced Mar 14, 2019
Merged
Parth1811
added a commit
to Parth1811/snare
that referenced
this issue
Mar 8, 2020
Handled the case when there is no proper host provided and also added tests for the cases when host provided has length less than 4 which indicates no proper domain was provided. Refs mushorg#187
Parth1811
added a commit
to Parth1811/snare
that referenced
this issue
Mar 8, 2020
Handled the case when there is no proper host provided and also added tests for the cases when host provided has length less than 4 which indicates no proper domain was provided. Refs mushorg#187
afeena
pushed a commit
that referenced
this issue
Mar 10, 2020
Handled the case when there is no proper host provided and also added tests for the cases when host provided has length less than 4 which indicates no proper domain was provided. Refs #187
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is plenty of opportunity to add more tests to SNARE. We make a lot of assumptions and with GSoC approaching, we should make sure the critical paths are covered.
The text was updated successfully, but these errors were encountered: