QA Valley has a Test Lab and dedicated quality assurance division specifically devoted to Compatibility Testing. This is a division consisting of QA Engineers and Technical Infrastructure exclusively allocated to evaluating the workability of Software Systems of Business Applications on different environments consisting of variations in Hardware Platforms, Operating Systems, Browsers, Databases, Peripherals, and other specialty software and components such as security and encryption that are essential to the operations of those systems / applications.
Compatibility Testing as performed by QA Valley, grades the performance of the software or application on environments that satisfy the recommended installation configurations. These configurations represent variations in components such as hardware, operating systems databases, browsers, etc., and are limited to component versions that are available to the target users. These limits in versions establish the boundaries of valid component variations or allowable environment configurations, and in turn result in a narrower universe of targeted or allowable users.
Compatibility Testing validates the behavior of the software on different environment configurations, and also encompasses backwards compatibility on selected critical components. It is generally expected that QA Valley performs backwards compatibility testing on selected components such as Operating Systems, Internet Browsers, and Databases. If is equally the case that QA Valley conducts forward compatibility testing on systems and applications as manufacturers release newer generations of hardware devices with more innovative feature sets.
Defects, gaps, and incompatibilities uncovered as a result of Compatibility Testing are recorded following the same practices QA Valley observes when conducting other types of testing. However, Compatibility Test results are more varied and diverse as a result of the permutations and combinations in environment configurations. Defects that are discovered in one browser or database version must be retested and documented on all other user accepted versions of those environment components, resulting in a larger repository of defects or incompatibility scenarios.