Skip to content

Commit 9b46e71

Browse files
committed
2nd round of review
1 parent 43f48db commit 9b46e71

File tree

2 files changed

+6
-9
lines changed

2 files changed

+6
-9
lines changed

monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -28,16 +28,13 @@ A `resources.communications.AuthAdapterResource` containing a second set of vali
2828

2929
This second set of credentials is required to validate that the DSS properly synchronizes the manager of a subscription to other DSS instances.
3030

31-
The participant under test is responsible for providing this second set of credentials along the primary ones used in most other scenarios.
31+
The test designer should provide this second set of credentials when full testing of manager synchronization behavior is desired.
3232

3333
#### Credential requirements
3434

3535
In general, these test credentials may be in all points equal to the ones used by the `AuthAdapterResource` that is
3636
provided to the `dss` resources above, except for the value contained in the `sub` claim of the token.
3737

38-
For the purpose of this scenario, these credentials must be allowed to create, modify and delete subscriptions on the DSS,
39-
as well as querying them.
40-
4138
Note that most checks in this scenario will work if the second set of credentials is not provided.
4239

4340
##### Required scope
@@ -46,7 +43,7 @@ For the purpose of this scenario, the `second_utm_auth` resource must provide ac
4643

4744
* `utm.strategic_coordination`
4845

49-
##### Separate subscription
46+
##### Separate subject
5047

5148
Note that the subject (or 'sub' claim) of the token that will be obtained for this resource
5249
MUST be different from the one of the `dss` resources mentioned above:
@@ -56,7 +53,7 @@ this will be verified at runtime, and the depending checks will not be run if th
5653

5754
### [Ensure clean workspace test step](../clean_workspace.md)
5855

59-
This step ensures that no subscriptions with the known test IDs exists in the DSS.
56+
This step ensures that no subscriptions with the known test IDs exist in the DSS.
6057

6158
This includes the main test subscription used in this test, as well as the extra subscription
6259
used for testing the `manager` field sync, if the test is configured to test for it.
@@ -274,7 +271,7 @@ As a result, the DSS pool under test is failing to meet **[astm.f3548.v21.DSS002
274271

275272
## [Cleanup](../clean_workspace.md)
276273

277-
This step ensures that no subscriptions with the known test IDs exists in the DSS.
274+
This step ensures that no subscriptions with the known test IDs remain in the DSS by deleting them at this point if they do exist.
278275

279276
This includes the main test subscription used in this test, as well as the extra subscription
280277
used for testing the `manager` field sync, if the test is configured to test for it.

monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,7 +208,7 @@ def run(self, context: ExecutionContext):
208208
"Skipping manager synchronization check: no extra credentials provided",
209209
)
210210

211-
self._step_mutate_subscriptions_secondaries_shift_time()
211+
self._repeat_steps_mutate_subscriptions_secondaries_shift_time()
212212

213213
self.begin_test_step("Delete subscription on primary")
214214
self._step_delete_sub()
@@ -687,7 +687,7 @@ def _step_mutate_subscriptions_broadcast_shift_time(self):
687687
new_params = sp.shift_time(timedelta(seconds=10))
688688
self._mutate_subscription_with_dss(self._dss, new_params, is_primary=True)
689689

690-
def _step_mutate_subscriptions_secondaries_shift_time(self):
690+
def _repeat_steps_mutate_subscriptions_secondaries_shift_time(self):
691691
"""Mutate the subscription on every secondary DSS by adding 10 seconds to its start and end times,
692692
then checking on every DSS that the response is valid and corresponds to the expected parameters."""
693693

0 commit comments

Comments
 (0)