-
Notifications
You must be signed in to change notification settings - Fork 671
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
Refactor the scapval test #10611
Refactor the scapval test #10611
Conversation
I propose to disregard CodeClimate suggestion, as the current layout allows us to easily add more conditions to the PASS case. |
tests/run_scapval.py
Outdated
return False | ||
|
||
|
||
def format_requirement_feedback(req_id, message): |
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 think it should be named print_requirement_feedback as its main goal is to print something, it doesn't return a formatted string.
- make it explicit that requirement ID refers to scapval - unify the print formatting code
Code Climate has analyzed commit 48f45ab and detected 1 issue on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 52.5% (0.0% change). View more on Code Climate. |
@jan-cerny , I believe it can already be merged, correct? |
@marcusburghardt Yes, it looks like the CI has already finished! |
Description:
Make the code more explicit/readable. Successor of #10451
Rationale:
Nothing in particular, make the code readable and extensible.
Review Hints:
The functionality should be the same.