{"id":4405,"date":"2013-12-06T16:43:01","date_gmt":"2013-12-06T21:43:01","guid":{"rendered":"http:\/\/www.iri.com\/blog\/?p=4405"},"modified":"2017-11-07T10:03:20","modified_gmt":"2017-11-07T15:03:20","slug":"tdm-primer","status":"publish","type":"post","link":"https:\/\/www.iri.com\/blog\/test-data\/tdm-primer\/","title":{"rendered":"Test Data Management: A Primer"},"content":{"rendered":"

Welcome to IRI’s primer on test data management. This is the opening article, which is followed by a 4-step series.
\n<\/em><\/p>\n

Introduction<\/h2>\n

As anyone familiar with the challenges of healthcare.gov<\/a> can tell you, complex application development requires an adequate period of formal testing, and comprehensive test data. The better and bigger your test data, the more reliable your new solutions and operations can be.<\/p>\n

\n
\"\"
“A lot of what we are seeing is not great data being sent from the marketplaces to the plans,” Sumit Nijhawan, the CEO of Infogix said. “The problem is more that you have a lot of data flying around to a lot of different entities. When you have something on this scale with this much data, issues are bound to happen.”<\/em><\/figcaption><\/figure><\/blockquote>\n

It is the goal of Test Data Management (TDM) to systematize the generation — and improve the quality, safety, and utility — of test data. TDM has become an IT imperative. According to the InfoSys white paper, “Test Data Management, Enabling Reliable Testing through Realistic Test Data:”<\/p>\n

Test teams not only have to follow exact test methodologies, but also ensure the accuracy of test data. They also need to ensure tests correctly reflect production situations, both functionally and technically.<\/em><\/p><\/blockquote>\n

Having the right sets of test data is important in many situations. For example:<\/p>\n