Would appreciate any input on how you currently test in your non-production tenants in regards to test data? Do you create example data, use some extract of real data and control its access, or possibly mask/obfuscate data?
Thank you.
Jeff we have three non-prod environments. We rotate through data refreshes every two weeks, so we always have an environment with data that is "current". We prepare by turning off scheduled jobs, and then run de-prod processes after the refresh to prevent actions from being emailed to individuals or vendors. Would be happy to share more if needed.
Dave,
Thank you so much for your reply. Are the de-prod processes items that your team has identified, or are they described by Infor? It sounds like the data copied to the non-prod environments is not masked? Do you have auditing enabled to capture who is accessing data while testing?
We identified these processes ourselves. We copy all prod data, including employees and vendors. Since we also have some of our production IPAs running in non-prod, we need to make sure we aren't sending emails to employees or vendors. So we do not mask or redact the data. We also utilize role-based security within our non-prod environments. There may be auditing available, but we do not have it enabled or use it.
Thank you Dave, appreciate you responses.
Hello, any other folks have techniques or procedures they employ for non-prod test data?
