In software testing, Data Migration Testing is conducted to compare migrated data with original data to discover any discrepancies when moving data from a legacy database(s) to a new destination database.
These data can be migrated either automatically using a migration tool or by manually extracting data from the source database and inserting the data into the destination database.
Data migration testing encompasses Data Level Validation testing and Application Level Validation testing.
Data Level Validation Testing:
This type of software testing verifies that data has been migrated from multiple databases to a common database without any discrepancies. The following levels of verifications will be performed during Data Level Validation Testing:
- Level 1
Row counts: Verify the number of records that will be migrated.
- Level 2
Data verification: Verify the accuracy of data of a selected sample from the migrated data.
- Level 3
Entitlement verification: Verify the destination database set up for users and data samples.
Application Level Validation Testing
In Application Level Validation testing, a software tester verifies the functionality of a sample migration application that was migrated from an old legacy system to the new system. Application Level Validation testing ensures smooth running of the migrated application with the new database using following validations:
- After migration, log in to the new application and verify a sample data set.
- After migration, log in to legacy systems and verify the locked/unlocked status of accounts.
- Verify customer support access to all legacy systems, despite the user being blocked during the migration process.
- Verify whether new users are prohibited from creating a new account in a legacy system after launching the new application.
- Verify immediate reinstatement of user access to the legacy system if migration to the new system fails.
- Verify the termination of access to legacy systems at migration.
- Validate system login credentials for the new application.
Test Approach for Data Migrating Testing
Data Validation Test Design
When you test database migration, it is important to create a set of SQL queries to validate the data before (source database) and after (destination database) migration. The validation queries can be arranged in a hierarchy and it should cover the designed scope.
For example, to test if all users have been migrated, it is essential to check how many users are in the source database and how many have been migrated. Checking the raw counts of each database will ensure this.
Take a sample data set from the source and compare the data with the destination data in the database.
- Always take the most important dataset and data that have values in all columns
- Verify the data types after the migration
- Check the different time formats/zones, currencies etc.
- Check for data with special characters
- Find data that should not be migrated
- Check for duplicated data after migration
A sample test case can be created as shown below:
|#||Test Description||Input Data||Source Query
|Expected Results||Test Results|
|1||Verify total count of migrated users||Not applicable||SELECT COUNT(*)
|Raw count should be same before and after the data migration.||Not Executed|
|2||Validate data of 5 rows in the user table||5 rows||SELECT *
WHERE ROWNUM <=5;
WHERE ROWNUM <=5;
|Data in the selected table rows should be identical before and after the migration.||Not Executed|
Test environments should consist of a source database copy and a blank isolated destination database. A tester can migrate data using a migration tool, which will facilitate the migration both table-by-table and using a set of reference tables. The tool should be able to accommodate a large data load since the data can include data from historical databases.
Data Validation Test Runs
The database migration process must be completed prior to the test depending on the test design.
If the migration test fails, it is important to report the bug with the following information:
- Number of failed rows and columns
- Name of the failed object
- Database error logs
- The query used to validate the data
- User account information used to run the validation
- Date and time of the test
- Semantic errors
Tips to Create an Effective Data Migration Test Approach
- Users should be able to access existing data and post migration data easily without any issues.
- Performance of database should be the same or better after the migration.
- Note the duration of the migration. A duration of a migration can be long, running the risk of application downtime.
- Have a copy of the source databases to conduct re-tests at any time on a new database. It will also help reproduce the bugs.
- Corrupted data should not be migrated to the destination database, and necessary actions should be taken to resolve the corrupted data.
- Get stakeholders involved the migration plan, as their permission to access different data sources could be mandatory.
- Make sure there are no inconsistencies in currency, date and time, time zone fields, and decimal points of currencies.
Click here to download our Software Testing brochurefor more information
Click here to read more about Brandix i3’s Software Testing and QA Solution
i3 Labs is the technology and innovations Lab at Brandix i3
From insights to thought-leadershipView More
Ensure Successful M3/CloudSuite Go-Live with a Robust Testing Strategy
Whether it’s a multi-site rollout or a minor fix, testing your ERP ensures that it works as expected. An error-free ERP implementation adds to the user experiences across the supply chain, and helps increase stakeholder productivity. A buggy, slow ERP can hinder operational efficiency. A carefully-planned ERP testing strategy ensures that the ERP performs optimally from the go-live itself, without hatching unprecedented errors, which not only require costly rework but also affect the smooth functioning of the organization’s operations.
Make your work meaningful with the power of Infor OS and Infor Document Management (IDM)
Infor OS is a cloud operating platform that seamlessly connects services to provide a robust integration framework. The scalable technologies on top of which Infor OS is built are capable of bringing together disparate technologies and solutions, whether it’s an application developed by Infor, by a third-party or in-house by your organization.
Moving to the Multi-Tenant Cloud: Busting the Top 3 Myths
We’re about to bust some serious myths about Infor’s multi-tenant cloud in this blog post—so brace yourself! Let’s start by demystifying the real difference between single-tenant and multi-tenant. Single-tenant is a single instance of the software and supporting infrastructure to serve a single customer, while multi-tenant means that a single instance of the software and its supporting infrastructure serves multiple customers.
#1724 – The Booth you need to visit at Inforum 2019!
Inforum 2019 has a lot to offer with rich content being discussed at speed sessions and guest talks, along with some of the industry’s best entertainers. With a week left to go - this Inforum, we’re giving you a few good reasons as to why you need to visit Booth #1724.