-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Test] Test the get_discoveries cli command #166
Conversation
…digger into feat/cli/get_discoveries
Hi @alaabenfatma, tests are failing so please fix the code. If tests fail I cannot start the code review |
The tests are failing. The possible reason (my guess) is that when you try to add discoveries you're not adding anything since the inserts break db rules, i.e., you can't add a discovery if you don't have the rule and the repo it references. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have 2 minor comments on style. Once fixed we can merge
discoveries = [] | ||
discoveries_count = 5 | ||
for state in ['new', 'false_positive', 'addressing', | ||
'not_relevant', 'fixed']: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wrong indentation (they should start below "new")
|
||
@classmethod | ||
def tearDownClass(cls): | ||
# Remove the repo and all its discoveries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
convert this into a docstring
discoveries = [] | ||
discoveries_count = 5 | ||
for state in ['new', 'false_positive', 'addressing', | ||
'not_relevant', 'fixed']: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment as in the other file
This PR targets
Note: Upon the merge of this PR, the previous PR (#164 ) can be closed since this one builds upon it. However, the latter PR can also be safely merged before this one as well (no conflicts will be raised nonetheless).
Feats: