You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we use string literals as expected test result in our unit tests:
classAtomicResult(TypedDict):
"""Expected atomic result of a unit test of an AntaTest subclass."""result: Literal["success", "failure", "skipped"]
classExpected(TypedDict):
"""Expected result of a unit test of an AntaTest subclass."""result: Literal["success", "failure", "skipped"]
Now that we have a AntaTestStatus we should use it instead:
classAtomicResult(TypedDict):
"""Expected atomic result of a unit test of an AntaTest subclass."""result: AntaTestStatus
classExpected(TypedDict):
"""Expected result of a unit test of an AntaTest subclass."""result: AntaTestStatus
NB: find a way to remove ERROR (an unexpected error has been caught by the ANTA framework, not by the test code) and UNSET (the test has never run) statuses that should not be expected in these test cases.
All the DATA variables must be refactored accordingly.
The text was updated successfully, but these errors were encountered:
mtache
changed the title
refactor: refactor unit tests DATA variables to use AntaTestStatus
refactor: unit tests DATA variables to use AntaTestStatus
Jan 7, 2025
Currently, we use string literals as expected test result in our unit tests:
Now that we have a
AntaTestStatus
we should use it instead:NB: find a way to remove ERROR (an unexpected error has been caught by the ANTA framework, not by the test code) and UNSET (the test has never run) statuses that should not be expected in these test cases.
All the DATA variables must be refactored accordingly.
The text was updated successfully, but these errors were encountered: