Closed mtruj013 closed 1 year ago
Merging #128 (f09ccad) into main (9ea893e) will increase coverage by
2.09%
. The diff coverage is99.25%
.:exclamation: Current head f09ccad differs from pull request most recent head 1b11eef. Consider uploading reports for the commit 1b11eef to get more accurate results
@@ Coverage Diff @@
## main #128 +/- ##
==========================================
+ Coverage 81.26% 83.35% +2.09%
==========================================
Files 28 29 +1
Lines 1297 1406 +109
==========================================
+ Hits 1054 1172 +118
+ Misses 243 234 -9
Flag | Coverage Δ | |
---|---|---|
python | 83.35% <99.25%> (+2.09%) |
:arrow_up: |
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files | Coverage Δ | |
---|---|---|
tests/fixtures/models.py | 100.00% <ø> (ø) |
|
...ons/versions/f18a0bd8a809_add_updated_at_column.py | 90.00% <90.00%> (ø) |
|
tests/fixtures/payloads.py | 100.00% <100.00%> (ø) |
|
tests/test_routes.py | 98.38% <100.00%> (+0.73%) |
:arrow_up: |
webapp/models.py | 84.78% <100.00%> (+0.11%) |
:arrow_up: |
webapp/schemas.py | 92.55% <100.00%> (+0.03%) |
:arrow_up: |
webapp/views.py | 77.36% <100.00%> (+3.74%) |
:arrow_up: |
Thanks all! @nottrobin could you take another look when you can?
Done
updated_at
column to CVE table to track time of update. On creation this field should default to the current timegroup_by
: Groups CVEs by priority (critical -> unknown)sort_by
: Sorts CVEs by publish or update dateorder
: Orders CVEs by descending or ascending values. This param used to only accept "oldest" as a value and this usage will now be depreciated.QA
Issue / Card
Fixes https://warthogs.atlassian.net/browse/WD-3200, https://warthogs.atlassian.net/browse/WD-3199