Test Data Management (TDM) Saktipada Behera - Automation Tester Reshma Pillai - Automation Tester Prathamesh Dewoolkar – Database Administrator Datamatics Global Services

Abstract Purpose of this white paper: TDM stands for Test Data Management. TDM reduces the effort involved in searching for the test data and execution of test scripts. This paper attempts to explain why testers need TDM for effective testing. Purpose of this white paper: Introduction Challenges faced without TDM TDM for Automation Testing How TDM Works Limitations in TDM Conclusion Key points addressed in this Deck:

Introduction Testing industry is looking for ways to optimize testing efforts and costs. Test Data Management is a potential area of improvement. Testing completeness and coverage depends mainly on the test data. Data analysis and data masking are main bottle neck for today’s data processing. Test data management supports above mentioned processes for a variety of sources. Being powerful and flexible test data rules designer, it supports documenting and archiving capabilities.

Challenges faced without TDM Each execution of scripts would require regular maintenance of test data. Requires more manual interaction. Risk of corrupted or used data. Abnormal termination of execution due to issues in test data. Increases the time for execution. 4

TDM for Automation Testing TDM is playing an important role in the testing industry. Earlier, test data was limited to few sample input files or manually searched and then hardcoded into the automation scripts. This consumed extra time and manual efforts. Now, all the major institutions rely on powerful test data containing unique combinations of data and which leads to highest coverage of testing. Structured approach to test all possible business scenarios. Provides best quality, suitable quantity, correct format test data at run time. Provides huge amount of test data during every execution.

How TDM Works Fast burning up of large amount of test data during test runs is a huge blocker for testing. Optimal data coverage is achieved by the TDM through intelligent tools and techniques. Automated processes lead to less work and reduced result replication time. Source: Datamatics Global Services

System requirements Dedicated local/cloud server Schema of test database. A common local database (SQL/Oracle), which can be access across the team. Batch/Script files for creating and accessing data from/to the database. Windows service to execute batch/script file on schedule time.

Test Data Creation Initially, Test data is not available hence, we need to create or get a data cut from production/test database (QA, UAT etc.). We can use batch/script files for creating sample data to the database by referring clone of production database. These batch files will execute automatically during off time by scheduling it. TDM will get a data cut from test database and store inside the local database which are specific to automation test projects. The data can also be created using user interface (UI) or via create or edit data operations in the database.

Fetching Data TDM will give the API to access the test data from local database at runtime during script execution by providing required inputs. TDM supports various Data sources like SQL, Oracle, MySQL, etc.

Limitations in TDM Requires sound knowledge of database structure. Maintenance of queries. (One time activity)

Conclusion TDM solutions saves time and cost as large volume of data will be available for every execution. Based on our learning and experience gained on TDM in automation testing, we can confidently affirm that higher coverage of test scenarios can be achieved easily. This tool helped to reduce about 15-20% execution time and fewer data related defects in test. About 40% of test cases used to fail due to incorrect or no test data. After implementation of the TDM, it helped in reducing more than 30% of script failure. It support various type of testing like, Web, Mobile, Desktop, API, Performance, robotics automations and etc.

Authors Biography Saktipada Behera Automation Tester Saktipada is working as an Automation Tester in DGSL. He has 5 of years technical experience in application Development and Testing. Being an Automation Tester he is responsible for various automation projects. He has completed BCA. Prior joining Datamatics, he had worked with HCL technology and Collabera technologies. He has sound domain knowledge in Insurance, Semiconductor & Education and so on.

Database Administrator Reshma Pillai Automation Tester Reshma is working as an Automation Tester in DGSL. She has 2 years of experience in Manual and Automation testing. Being a Tester she is responsible for various testing projects. She has completed BSc IT from Mumbai University and certified professional Selenium Automation Testing from ATA. She has sound domain knowledge in Insurance. Prathamesh Dewoolkar Database Administrator Prathamesh is working as a Database Administrator in DGSL. He has 2 years technical experience in Database management. Being a DBA he is responsible for managing various test databases. He has completed BSc IT from Mumbai University. He has sound domain knowledge in Insurance.

Thankyou!