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
Copy file name to clipboardExpand all lines: test/postman/ClearPostmanData.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ clear the test data from postman test completed!
34
34
info: Done!
35
35
```
36
36
## Strategy
37
-
1. Setup the `POSTMAN_ROLE_NAME_PREFIX` from the test environment. This prefix should be a name that will never be used
37
+
1. Setup the `AUTOMATED_TESTING_NAME_PREFIX` from the test environment. This prefix should be a name that will never be used
38
38
set as part of the role name. e.g. 'POSTMANE2E-'. In this case, the created `ResourceRole` will have a name like 'POSTMANE2E-submitter'.
39
39
40
40
2. Choose either one solution for mocking the Bus API. We can not ignore this, becuase in production environment, it is
@@ -45,7 +45,7 @@ b. You can use use Postman's mock server. You can refer to https://drive.google.
45
45
for details. You need to update the environment variable `BUSAPI_URL` to your Postman mock server.
46
46
47
47
3. Steps of clearing the test data from Postman tests.
48
-
* Find all `ResourceRole` record whose names are starting with `POSTMAN_ROLE_NAME_PREFIX`.
48
+
* Find all `ResourceRole` record whose names are starting with `AUTOMATED_TESTING_NAME_PREFIX`.
49
49
* For each `ResourceRole` record, find all `ResourceRolePhaseDependency` records whose `resourceRoleId` are the same
50
50
as the `id` of `RecourceRole`. Delete those `ResourceRolePhaseDependency` records.
51
51
* For each `ResourceRole` record, find all `Resource` records whose `roleId` are the same
@@ -66,4 +66,4 @@ b. You can use use Postman's mock server. You can refer to https://drive.google.
66
66
* Existing production data should not be affected by the tests. You need to suggest how to avoid this possible issue.
67
67
_Check the strategy section. All testing data are removed at last._
68
68
* If possible, we should be able to differentiate the test data from the actual data so we can filter it out from the search results of the production API. Please suggest how to achieve this.
69
-
_Check the strategy section. We can easy find all `ResourceRole` records with the given role name prefix. Then we can find all the related `ResourceRolePhaseDependency` and `Resource`._
69
+
_Check the strategy section. We can easy find all `ResourceRole` records with the given role name prefix. Then we can find all the related `ResourceRolePhaseDependency` and `Resource`._
0 commit comments