What is Portability Testing?

- Portability Testing is the testing of a software/component/application to determine the ease with which it can be moved from one machine platform to another. 

- In other words, it’s a process to verify the extent to which that software implementation will be processed the same way by different processors as the one it was developed on.  

- It can also be understood as amount of work done or efforts made in order to move software from one environment to another without making any changes or modifications to the source code but in real world this is seldom possible.

- For example, moving a computer application from Windows XP environment to Windows 7 environment, thereby measuring the efforts and time required to make the move and hence determining whether it is re usable with ease or not.

- Portability testing is also considered to be one of the sub parts of System testing as this covers the complete testing of software and also it’s re-usability over different computer environments that include different Operating systems, web browsers.

What needs to be done before Portability testing is performed (pre requisites/pre conditions)? 

1.   Keep in mind portability requirements before designing and coding of software.

2.   Unit and Integration Testing must have been performed.

3.   Test environment has been set up.

Objectives of Portability Testing

1. To validate the system partially i.e. to determine if the system under consideration fulfills the portability requirements and can be ported to environments with different :-

a). RAM and disk space

b). Processor and Processor speed

c). Screen resolution

d). Operating system and its version in use.

e). Browser and its version in use.

To ensure that the look and feel of the web pages is similar and functional in the various browser types and their versions.

2.   To identify the causes of failures regarding the portability requirements, this in turn helps in identifying the flaws that were not found during unit and integration testing.

3.   The failures must be reported to the development teams so that the associated flaws can be fixed.

4.   To determine the potential or extent to which the software is ready for launch.

5.   Help in providing project status metrics (e.g., percentage of use case paths that were successfully tested).

6.   To provide input to the defect trend analysis effort.