Test participant(s) not indicated for NET0210 #244
Assignees
Labels
Comments
BenjaminPelletier
added
bug
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 12, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 12, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
Shastick
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 13, 2023
mickmis
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 20, 2023
mickmis
added a commit
to Orbitalize/monitoring
that referenced
this issue
Oct 20, 2023
BenjaminPelletier
pushed a commit
that referenced
this issue
Oct 20, 2023
…some refactorings and fixes (#247) * [uss_qualifier] attach participant id to net0210 check, fix Issue #244 * rename server_id -> participant_id * factor out polling; refactor some parts of scenarios * add aud override in NoAuth * fix participant_id setter * fix several issues * fix small issues * add TODO --------- Co-authored-by: Mickaël Misbach <[email protected]> Co-authored-by: Mickaël Misbach <[email protected]>
github-actions bot
added a commit
that referenced
this issue
Oct 20, 2023
…some refactorings and fixes (#247) * [uss_qualifier] attach participant id to net0210 check, fix Issue #244 * rename server_id -> participant_id * factor out polling; refactor some parts of scenarios * add aud override in NoAuth * fix participant_id setter * fix several issues * fix small issues * add TODO --------- Co-authored-by: Mickaël Misbach <[email protected]> Co-authored-by: Mickaël Misbach <[email protected]> 9753ad1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When the check for "Missing credentials" is performed, no participant ID is indicated, so the success or failure of that check cannot be attributed to any participant in the scenario (no one can take credit for it).
To reproduce
See output/tested_requirements_uspace/uss1.html from one of the CI runs and note that NET0210 is not marked as passed. Then, see the misbehavior scenario in output/sequence_uspace and see that the check is performed, it's just not attributed to any USS.
Difference from expected behavior
I expect nearly all (possibly just "all" period) checks to be associated with a test participant so that test participant can take credit for verifying compliance to that requirement.
Possible solution
Each time the "Missing credentials" check is performed, indicate which test participant could be failing to meet the requirement if it doesn't pass.
Codebase information
Issue as of 5d7821e
The text was updated successfully, but these errors were encountered: