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: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,14 +148,14 @@ Test data is created before running tests using the `/api/testing/onboard` endpo
148
148
1. For each programme group (HPV, Flu, Doubles, MMR)
149
149
1. A random valid year group is selected.
150
150
2. Two random valid schools that have this year group are retrieved using the MAVIS `/api/testing/locations` endpoint.
151
-
3. User, team, and organisation data is generated by the test worker.
152
-
4. The school, user, team, and organisation data is sent to the MAVIS `/api/testing/onboard` endpoint, inserting all of this data into the database and linking the schools to the team.
153
-
5. The test worker also generates two children which are not immediately added to the database but can be imported later.
154
-
2. The generated test data is provided as a set of fixtures, which can be injected into tests (or other fixtures). Some common examples:
151
+
2. User, team, and organisation data is generated by the test worker.
152
+
3. The school, user, team, and organisation data is sent to the MAVIS `/api/testing/onboard` endpoint, inserting all of this data into the database and linking the schools to the team.
153
+
4. The test worker also generates two children for each programme which are not immediately added to the database but can be imported later.
154
+
5. The generated test data is provided as a set of fixtures, which can be injected into tests (or other fixtures). Some common examples:
155
155
- `children` – provides two children for each programme group (in the form of a map)
156
156
- `schools` – provides two schools for each programme group (also in the form of a map)
157
-
3. After a test module has finished, the worker clears out any data created by running the test module by calling the MAVIS `/api/testing/teams/<workgroup>` endpoint with parameter `keep_itself=true`.
158
-
4. After a worker has finished running all test modules allocated to it, it calls the MAVIS `/api/testing/teams/<workgroup>` endpoint without the `keep_itself` parameter, which clears all associated with the team used by the worker including the team itself. No data should remain after a test run.
157
+
6. After a test module has finished, the worker clears out any data created by running the test module by calling the MAVIS `/api/testing/teams/<workgroup>` endpoint with parameter `keep_itself=true`.
158
+
7. After a worker has finished running all test modules allocated to it, it calls the MAVIS `/api/testing/teams/<workgroup>` endpoint without the `keep_itself` parameter, which clears all associated with the team used by the worker including the team itself. No data should remain after a test run.
0 commit comments