-
Notifications
You must be signed in to change notification settings - Fork 20
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
[uss_qualifier] expand the authentication validation scenario to include constraint reference endpoints #690
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -22,6 +22,7 @@ At least one of the following scopes needs to be available for this scenario to | |||||
|
||||||
- `utm.strategic_coordination` | ||||||
- `utm.availability_arbitration` | ||||||
- `utm.constraint_management` | ||||||
|
||||||
In order to verify each endpoint group, all scopes above must be available. | ||||||
|
||||||
|
@@ -387,6 +388,158 @@ it is in violation of **[astm.f3548.v21.DSS0100,1](../../../../../requirements/a | |||||
The response to a successful USS Availability Set request is expected to conform to the format defined by the OpenAPI specification under the `A3.1` Annex of ASTM F3548−21, | ||||||
otherwise, the DSS is failing to implement **[astm.f3548.v21.DSS0100,1](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
### Constraint reference endpoints authentication test step | ||||||
|
||||||
#### 🛑 Unauthorized requests return the proper error message body check | ||||||
|
||||||
If the DSS under test does not return a proper error message body when an unauthorized request is received, | ||||||
it fails to properly implement the OpenAPI specification that is part of **[astm.f3548.v21.DSS0005,3](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Create constraint reference with missing credentials check | ||||||
|
||||||
If the DSS under test allows the creation of a constraint reference without any credentials being presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Create constraint reference with invalid credentials check | ||||||
|
||||||
If the DSS under test allows the creation of a constraint reference with credentials that are well-formed but invalid, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Create constraint reference with missing scope check | ||||||
|
||||||
If the DSS under test allows the creation of a constraint reference with valid credentials but a missing scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Create constraint reference with incorrect scope check | ||||||
|
||||||
If the DSS under test allows the creation of a constraint reference with valid credentials but an incorrect scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Create constraint reference with valid credentials check | ||||||
|
||||||
If the DSS does not allow the creation of a constraint reference when valid credentials are presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I believe this should be:
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still 1? |
||||||
|
||||||
#### [Create response format](../fragments/cr/crud/create_format.md) | ||||||
|
||||||
Check response format of a creation request. | ||||||
|
||||||
#### 🛑 Get constraint reference with missing credentials check | ||||||
|
||||||
If the DSS under test allows the fetching of a constraint reference without any credentials being presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Get constraint reference with invalid credentials check | ||||||
|
||||||
If the DSS under test allows the fetching of a constraint reference with credentials that are well-formed but invalid, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Get constraint reference with missing scope check | ||||||
|
||||||
If the DSS under test allows the fetching of a constraint reference with valid credentials but a missing scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Get constraint reference with incorrect scope check | ||||||
|
||||||
If the DSS under test allows the fetching of a constraint reference with valid credentials but an incorrect scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Get constraint reference with valid credentials check | ||||||
|
||||||
If the DSS does not allow fetching a constraint reference when valid credentials are presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also: no checking of the get response format? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch. Added to the validator. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still 1? |
||||||
|
||||||
#### [Read response format](../fragments/cr/crud/read_format.md) | ||||||
|
||||||
Check response format of a mutation. | ||||||
|
||||||
#### 🛑 Mutate constraint reference with missing credentials check | ||||||
|
||||||
If the DSS under test allows the mutation of a constraint reference without any credentials being presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Mutate constraint reference with invalid credentials check | ||||||
|
||||||
If the DSS under test allows the mutation of a constraint reference with credentials that are well-formed but invalid, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Mutate constraint reference with missing scope check | ||||||
|
||||||
If the DSS under test allows the mutation of a constraint reference with valid credentials but a missing scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Mutate constraint reference with incorrect scope check | ||||||
|
||||||
If the DSS under test allows the mutation of a constraint reference with valid credentials but an incorrect scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Mutate constraint reference with valid credentials check | ||||||
|
||||||
If the DSS does not allow the mutation of a constraint reference when valid credentials are presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0005,3](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### [Mutate response format](../fragments/cr/crud/update_format.md) | ||||||
|
||||||
Check response format of a mutation. | ||||||
|
||||||
#### 🛑 Delete constraint reference with missing credentials check | ||||||
|
||||||
If the DSS under test allows the deletion of a constraint reference without any credentials being presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Delete constraint reference with invalid credentials check | ||||||
|
||||||
If the DSS under test allows the deletion of a constraint reference with credentials that are well-formed but invalid, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Delete constraint reference with missing scope check | ||||||
|
||||||
If the DSS under test allows the deletion of a constraint reference with valid credentials but a missing scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Delete constraint reference with incorrect scope check | ||||||
|
||||||
If the DSS under test allows the deletion of a constraint reference with valid credentials but an incorrect scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Delete constraint reference with valid credentials check | ||||||
|
||||||
If the DSS does not allow the deletion of a constraint reference when valid credentials are presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0005,1](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, no checking of delete response format? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Still 1? |
||||||
|
||||||
#### [Delete response format](../fragments/cr/crud/delete_format.md) | ||||||
|
||||||
Check response format of a deletion. | ||||||
|
||||||
#### 🛑 Search constraint references with missing credentials check | ||||||
|
||||||
If the DSS under test allows searching for constraint references without any credentials being presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Search constraint references with invalid credentials check | ||||||
|
||||||
If the DSS under test allows searching for constraint references with credentials that are well-formed but invalid, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Search constraint references with missing scope check | ||||||
|
||||||
If the DSS under test allows searching for constraint references with valid credentials but a missing scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Search constraint references with incorrect scope check | ||||||
|
||||||
If the DSS under test allows searching for constraint references with valid credentials but an incorrect scope, | ||||||
it is in violation of **[astm.f3548.v21.DSS0210,A2-7-2,7](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### 🛑 Search constraint references with valid credentials check | ||||||
|
||||||
If the DSS does not allow searching for constraint references when valid credentials are presented, | ||||||
it is in violation of **[astm.f3548.v21.DSS0005,4](../../../../../requirements/astm/f3548/v21.md)**. | ||||||
|
||||||
#### [Search response format](../fragments/cr/crud/search_format.md) | ||||||
|
||||||
Check response format of a search. | ||||||
|
||||||
## [Cleanup](../clean_workspace.md) | ||||||
|
||||||
### [Availability can be requested](../fragments/availability/read.md) | ||||||
|
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.
Probably not the highest priority for adjustment, but It seems like the "steps" in this scenario should actually be "cases". A step is supposed to be a single logical action (do one thing), reflecting what a manual checkout test card would look like ("(step 1) Ok, now we're going to X -- did things Q and P happen? (step 2) Now we're going Y -- did things R and S happen?"). I would imagine a good test case would be "test authentication of all the constraint management endpoints", and then each testing of each constraint management endpoint would be a test step (or, testing of each constraint management endpoint in a particular way would be a test step).
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.
This makes sense. it might be possible to easily do this as part of this PR, as I need to handle the optional
utm.constraint_processing
scopes, but I'm not entirely sure yet.(Replacing the current steps with a test case having a single step would be easy in any case: I might keep splitting each test case into proper steps for later)
I created #742 to keep track of it in any case.
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.
Given the current priorities I'll leave the splitting into separate test cases for later.