Problems with test data
I looked for a similar case here in the forums and around the web but I couldn't find, so I will ask here.
The company I work for has currently one development environment and two test environment, all of them are snapshots from the production environment, which means all the environment data is copied three times.
They are upgrading to two dev environments and three test environment, plus one training environment. Since production data is now around 30TB, they are looking for means to use only a fraction of those. But the problem is, there are several systems integrated, some of them consult tables without the proper references, so it's almost impossible for a tool to map all the relations between tables and applications.
Does anyone know about a similar problem, and/or solutions for it? Thanks a lot.
Re: Problems with test data
When I moved data into my QA environment I had a job set to scrub specific tables, but it took awhile to understand what tables we could scrub. I also took the time to do things like remove certain personal information, especially email addresses (which were all changed to a local default) so that while testing there was no accidental email being sent to Customers.
You'll probably need different requirements for your different environments, work on what you need for each one and then start scubbing. It may take time, especially if the dependencies are not understood, since you'll probably have to make a change them run tests and see if things are broken.
Nothing learns better than experience.
"So as I struggle with this issue I am confronted with the reality that noting is perfect."
Now wasting blog space at QAForums Blogs - The Lookout