Back in September, we discussed the possibility of replicating and anonymising Production data to testing environments, however, this was rejected by the Developers due to risk factors such as data not being fully anonymised and also that the anonymisation process might be problematic. This ticket is to consider other solutions to the issue whereby we might be able to generate realistic, fully populated candidate applications for testing on Develop and Staging.
User Story
As the Digital team, I would like to be able to generate realistic dummy application data so that I can test new and old functionality on the platform.
Benefit(s) to user (if not already clear from User story)
Provides assurance to Digital team and Admins that new features actually work with real applications.
Feature(s) Description
Clearly describe the new functionality/change(s) to existing functionality.
Include a link to a Miro board/image if appropriate.
[ ] Feature
Acceptance Criteria
Specify the requirements of the primary user(s) for the change, update, or new feature - use the format:
It's done when...
Definition of Done
[ ] User stories/acceptance criteria met
[ ] Internal reviews passed (feedback actioned)
[ ] User testing passed
[ ] Relevant technical documentation updated
[ ] User guidance updated
[ ] Deployed and merged without errors
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Background
Back in September, we discussed the possibility of replicating and anonymising Production data to testing environments, however, this was rejected by the Developers due to risk factors such as data not being fully anonymised and also that the anonymisation process might be problematic. This ticket is to consider other solutions to the issue whereby we might be able to generate realistic, fully populated candidate applications for testing on Develop and Staging.
User Story
As the Digital team, I would like to be able to generate realistic dummy application data so that I can test new and old functionality on the platform.
Benefit(s) to user (if not already clear from User story)
Feature(s) Description
Clearly describe the new functionality/change(s) to existing functionality. Include a link to a Miro board/image if appropriate.
Acceptance Criteria
Specify the requirements of the primary user(s) for the change, update, or new feature - use the format: It's done when...
Definition of Done
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion