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
Background
Whilst efforts to generate dummy data for use on Develop and Staging environments have been helpful, the dummy data does not fully facilitate the testing of new features - the use of actual exercise data would ensure testing was much more accurate. Additionally, sometimes errors result from the dummy data. However, the solution must provide a sure-fire way of anonymising specific personal data, e.g. name, email address, NINO.
User Story
As the Digital team, we would like to be able to work with real data in Develop and Staging environments so that testing of new features is more accurate and errors are not introduced due to data.
Feature(s) Description
This is a spike only.
Estimate
Medium = 2-5 days - M
The text was updated successfully, but these errors were encountered:
It is not agreed that we should implement this. Developers are worried about the risk of copying data from production and also thinking the anonimisation might remove problematic data
Background
Whilst efforts to generate dummy data for use on Develop and Staging environments have been helpful, the dummy data does not fully facilitate the testing of new features - the use of actual exercise data would ensure testing was much more accurate. Additionally, sometimes errors result from the dummy data. However, the solution must provide a sure-fire way of anonymising specific personal data, e.g. name, email address, NINO.
User Story
As the Digital team, we would like to be able to work with real data in Develop and Staging environments so that testing of new features is more accurate and errors are not introduced due to data.
Feature(s) Description
This is a spike only.
Estimate
Medium = 2-5 days - M
The text was updated successfully, but these errors were encountered: