In-depth and reliable analysis is essential to identify required type of test data, where those can be located, how the required test data can be gathered etc. It is very important to include variety of test data types in the list of required type of test data. Because it helps to test the software on different aspects and qualities. Required test data can be on several places such as in databases stored in same premise or deviated geographically. There should be a convenient plan to gather those test data which often involves contacting database administrators and business owners. Analysis also includes identifying patterns of the test data. After patterns are identified, the test data can be automated by using automated test data creation tool which is significant save on the time, effort and cost.
There are expected challengers to face during test data management process. The common challengers are test data redundancy, test data subsetting, storing test data etc. Test data redundancy often happens due to possibilities of that the same data can be in different databases in different formats. Test data is categorized depending on software testing requirements that can relate to test data volume, formats, validity of test data (may attached with dates) and many. Usual software development organizations consist of two parties that utilize test data as a major asset who are the software developing team and software testing team. It costs heavy and even can be unnecessary to have two databases with same test data within an organization for two parties to use. Many software development companies only have one database that contains test data as a cost management procedure. When particular party is in need of access to test data, that party should reserve database ahead of the time which called as test data bookings in software engineering terminology.
Ref : http://enov8.jimdo.com/2014/03/20/test-data-analysis-and-test-data-management-challengers/