Closed JeremykJAC closed 2 years ago
We need to go a lot further with cleaning the dummy data. Plus please ensure it is not publicly accessible!
I have deleted the file shared in the PR.
Would suggest at least the following additional steps however please use your own diligence to ensure that no personal or identifiable data is used:
@jac-dummy-email.jac
To do
Create a bank of testing data, from production. 3,000 candidates that will have some of their information obscured, for security (phone number and email address to contain random characters at the end i.e. jeremy123@judicial) Hold this data in the db to be called upon when needed to fill in an exercise with relevant/real information.
All our test data will have the same login password, but unique email addresses. This will allow us to login as any user on Apply for testing purposes.
Acceptance criteria
Generate a bank of test data
[x] 3,000 records from prod to be stored here xxx
[x] Change applicants phone numbers to 08000 000 000
[x] Add sequential numbers to the end of their email address before the @ i.e. Justin123@, Barbara124@, Lawrence125
[x] Generate the same password for each applicant (send this to developers in Slack)
Load test application data
[x] When an exercise is published and approved a Create test applications button will appear
[x] When this button is selected a pop up appears to select applicant number. Chose between 1-3,000 then test applications will be generated from xxx
[x] Once successful the Success! button will appear and then move to Process late applications. (this is the usual flow)
Design
Create test applications button
Choose application number
Success state
Applications table