

This article is part of a 4-step series introduced here. Navigation between articles is below.
Step 2: Test Data Needs Assessment
Once the questions of who needs test data for what — and who will be dealing with it along its lifecycle are answered (see Step 1) — a deeper dive is needed into the specific technical aspects of the data itself.
Read MoreThis article is part of a 4-step series introduced here. Navigation between articles is below.
Step 1: Goal Setting & Team BuildingSomeone needs test data to do something, like:
stress-testing the functions and performance of applications prototyping database load/query and DW ETL/ELT operations benchmarking prospective new hardware or software outsourcing development or proofs of concept demonstrating systems with real-looking, but not real, sample dataIn all these cases, the most realistic data possible is needed, but it should also be safe and de-personalized.
Read MoreWelcome to IRI’s primer on test data management. This is the opening article, which is followed by a 4-step series.
IntroductionAs anyone familiar with the challenges of healthcare.gov can tell you, complex application development requires an adequate period of formal testing, and comprehensive test data.
Read More