Repository navigation
doc(anta.tests): Use advisory assessment states in SA test docstrings - #1857
carl-baillargeon merged 2 commits into
Conversation
Replace Success/Failure labels in security advisory test docstrings with the advisory assessment states (Not Affected, Affected, Mitigated, Inconclusive, Error), standardize the docstring layout on Expected Results, optional Notes, and Examples, and add a unit test enforcing it.
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
gmuloc
left a comment
There was a problem hiding this comment.
LGTM except couple of nits
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1857 +/- ##
==========================================
+ Coverage 95.38% 95.39% +0.01%
==========================================
Files 172 172
Lines 17220 17261 +41
Branches 2636 2644 +8
==========================================
+ Hits 16425 16466 +41
Misses 480 480
Partials 315 315
🚀 New features to boost your workflow:
|



Description
Security advisory test docstrings now describe outcomes with the advisory assessment states instead of ANTA test statuses, and follow one consistent layout.
Expected Resultsbullets use Not Affected, Affected, Mitigated, Inconclusive, and Error, inAdvisoryStatusorder, and state only the condition for each outcome.Notessection afterExpected Results. Previously, rationale written after the bullets rendered inside the Expected Results block on the docs site.docs/security-advisory/tests.mdexplains how these states map to ANTA statuses.test_advisory_docstring_layoutunit test enforces the layout and labels.Fixes #1757
Checklist
pre-commit run)tox -e testenv)Summary by CodeRabbit
Documentation
Tests