Overview of Conversion Testing in Software Testing

Conversion Testing :
Every software development process follows the Software Development Life Cycle (SDLC) for developing and delivering a good quality software product. In the testing phase of software development, different types of software testing are performed to check different check parameters or test cases. Where in each software data is an important part as with the help of data a software application performs its operations. Conversion Testing is done to verify the conversion of one data format to another data format that can be used continuously by an application under the test process. Any type of data can be converted from one form to another form, but the web pages must be in HTML format so that the browser can easily render the page.

Some common Test Examples :

• Button Color –
  For example, we test whether a blue button converts at a higher rate than a red button.
• Background Image –
  For example, it tests whether a background image converts at a higher rate than a normal plain image.
• Offer –
  For example, it tests whether free shipping of products of $50 or less, converts higher than 10% discount.
• Pop Up –
  For example, it tests whether a pop-up converts at a higher rate rather than a flyout for mobile visitors.

A/B Tests v/s Sequential Tests  :

1. A/B Test is simply creating two versions of something. It automatically accounts for all the factors because there is only difference between a set of visitors from other from others is what they see on your site, meanwhile time, year, and weather are the same i.e. restricting outside activities that may influence the result.
2. On the other hand in sequential testing, we are doing one thing for some time and if we make some changes we would leave them for the same period, then we can easily compare results. But in this case, it is correctly analyzed because many factors could have altered the results that may be out of control.

Levels of Data Conversion Testing :
There are mainly two levels of testing done i.e. technically & business “warm and fuzzy testing”. Technical testing will check conversion against the specs while business testing will give business representatives confidence when their old systemise in at rest, the precious data copied flawlessly to the new system.

1. Technical Testing :

We should initiate this testing by establishing test traceability. At least one test should be written against each statement as previously to ensure the test will cover all the data to be converted. We should initiate this testing by establishing test traceability. At least one test should be written against each statement as previously to ensure the test will cover all the data to be converted.

We can write queries in many ways to test whether a particular record is correctly converted. 

There are mainly two most common queries:

• (i) Row Count
• (ii) Identify objects with missing data

(i) Row Count –
They are used to compare the number of records in the source & target table. If the conversion is straight conversion, the above queries can easily check no. of rows.  If records with particular parameter is to be converted then we may follow run following queries.

Run against Source Table,
Choose count(*) from [Source table]
where [field1] = [a condition]
          [field2] = [another condition]
Run against Target Table,
Choose count(*) from [Target table]

 This test will give you no. of subsets of the source table that are to be converted and the total number. of rows in the target table. The test passes if the numbers match.

(ii) Identify objects with Missing Data –
Its focus is to identify parent objects whose child objects that should have been converted are absent. It tests each parent has their corresponding child object we write the SQL query in the following steps.

a. Write a query that will get the foreign key that goes back to the the parent table from child objects table. e.g.

where  [field1] = [value1] AND
 [field2] = [value2] AND
 [field3] = [value3]

Here this will provide all the correctly connected child objects.

b. Write a query for the parent table that get all the parent_id’s that should be  child object in ChildObjectTable e.g.

choose id from parentTable
where [fieldX] = [a value]

      c.  Now we combine the two queries which will help in generating a new query to display parent_id’s that didn’t exist in the first query. e.g.

select id from parentTable
where [fieldX] = [some value] and
id  is not in (
select parent_id from childObjectTable
where [field1] = [value1] AND
           [field2] = [value2] AND
           [field3] = [value3]
)

So the list will generate a list of entire parent_id’s that are missing a correctly generated child object from childObjectTable.

2. Business Testing :

• The business test once identified can be done by either using SQL service or by running GUI tests. In this testing business personnel will know what looking for in the old system and by following the actions in the test, we can demonstrate that the data they are interested in is converted accurately.
• So here they would write a test like that of a functional test which includes navigation through the system etc. which will show the data in the system.

Advantages of Conversion Testing :

• Accuracy of data transfer: Conversion testing ensures accurate and reliable data transfer between systems without loss or corruption.
• Improved efficiency: Identification and resolution of issues in the conversion process lead to a streamlined and efficient conversion process.
• Cost-effectiveness: Early detection and resolution of issues in conversion testing prevent costly delays and failures during the implementation phase.
• Compliance with regulations: Conversion testing ensures that data transferred between systems meets regulatory and industry standards, particularly for data privacy and security.
• Improved system quality: Conversion testing verifies the completeness, accuracy, and validity of transferred data, enhancing the overall quality and reliability of the new system.
• Increased customer satisfaction: Conversion testing reduces errors and delays, instilling customer confidence in the accuracy and integrity of their data in the new system.
• Reduced project risks: Thorough conversion testing identifies and mitigates risks associated with data conversion, minimizing the chances of project delays or failures.

Disadvantages of Conversion Testing :

• Cost: Conversion testing can incur additional expenses due to the need for resources, tools, and infrastructure.
• Complexity: Managing the complexity of data mapping, transformation, and validation can pose challenges during conversion testing.
• Testing limitations: Not all scenarios or edge cases may be covered in conversion testing, potentially leading to overlooked issues.
• Data security: Handling sensitive and confidential data during conversion testing raises concerns about data security and privacy.
• User resistance: Users may resist the new system or the conversion process, impacting the effectiveness of conversion testing and project success.
• System compatibility: Compatibility issues between the new system and existing systems or applications may arise, requiring additional effort to resolve.