Test Data Management
Test Data Management
It is a process of organizing this data to ensure that it is input correctly and the results are
reported properly. It also ensures sensitive information is processed securely during testing phase
.As the testing process generate huge volume of data using test data management can reduce cost
and time consuming errors and help tester clearly understand the jobs.The main objective of the
test data management is to check and test the quality of the software. It separates the test data
from production data. It minimizes and optimizes the size of software testing data and creates the
testing reports. To implement the process of the test data management, test data tool is used.
Any test data management tool follows the following steps of processing:
➢ In any system, data is stored in different formats, types, and locations. Different rules are
applied to this data. Hence, the test tool finds out the appropriate test data from these data
for the testing process.
➢ Now the tool extracts the subset of data from the selected test data collected from
multiple data sources.
➢ After selecting the subset test data, test tool uses masking for sensitive test data, such as a
client’s personal information.
➢ Now the tool performs the comparison between the actual data and baseline test data to
check the accuracy of the application.
➢ To increase the efficiency of the application, the tool refreshes the test data.
Test data
➢ It is the information used as the input of a test case. It is the fact that data preparing is the
time consuming and hardest phase in software testing. Referring to a study conducted by
IBM in 2016, searching, managing, maintaining, and generating test data encompass
30%-60% of the testers time.
Test data can be grouped according to different parameters. As for their importance, there can be
distinguished:
➢ test-specific data: influence the system behavior and reveal the case specifics under the
test
➢ test-reference data: have little influence on the test performance
➢ application reference data: irrelevant to the behavior under test, and are needed to start
the application
Test data commonly include the following types
➢ Valid test data. It is necessary to verify whether the system functions are in compliance
with the requirements, and the system processes and stores the data as intended.
➢ Invalid test data. QA engineers should inspect whether the software correctly processes
invalid values, shows the relevant messages, and notifies the user that the data are
improper.
➢ Boundary test data. Help to reveal the defects connected with processing boundary
values.
➢ Wrong data. Testers have to check how the system reacts on entering the data of
inappropriate format, whether it shows the correct error messages.
➢ Absent data. It is a good practice to verify how the product handles entering a blank
field in the course of software testing.
➢ Data validity and consistency-How old the data? Where it come from? Can you guarantee
its integrity?
➢ Data privacy-Are you adhering to government and industry regulations? Are you
safeguarding customer privacy? Are you protecting your data?
➢ Data selection and subsetting-Can you scale down the production environment and
choose a representative subset of data Is your selection process effective?
➢ Additional time for data set up/management instead of actual testing
➢ Additional administrative efforts in test data management
➢ Additional expense including personnel and hardware
➢ Inaccurate/difficult to access data negatively impacts testing
➢ Sensitivity of private information (credit cards, medical records, etc.)
➢ Storage required for test data
➢ Potential for data loss
➢ Use of real data versus fake data generated from scratch
➢ Data requests poorly communicated result in inadequate data returns
➢ Test data coverage is often incomplete and the team maynot have required knowledge
Ways to create the test data
➢ Manually
➢ Import from the production environment
➢ Duplication from prior customer systems
➢ Using test automation tools
What is Test Data Generation? Why test data should be created before test execution?
Depending on your testing environment you may need to CREATE Test Data (Most of the
times) or at least identify a suitable test data for your test cases (is the test data is already
created).Typically test data is created in-sync with the test case it is intended to be used for.
• Manually
• Mass copy of data from production to testing environment
• Mass copy of test data from legacy client systems
• Automated Test Data Generation Tools
Typically sample data should be generated before you begin test execution because it is difficult
to handle test data management otherwise. Since in many testing environments creating test
data takes many pre-steps or test environment configurations which is very time-
consuming.