Why Configuration Testing?

by Nataliia Vasylyna | August 5, 2015 12:36 pm

Any member of the software testing company knows that configuration testing is a testing technique that evaluates the work of a program taking into account the different system configurations.

Configuration testing has 2 main objectives – if the project is aimed at studying the conditions of the system’s migration from one platform to another, then the verification of a system for compatibility with other software or equipment indicated in the specification is performed.

If the project aims to determine the profile of the system’s work, the tester should spot the most efficient hardware configuration that will provide the desired performance characteristics.

In addition, experts recommend the use of the automated testing[1] elements as a supplement to the configuration testing in order to reduce time-consuming.

Two Basic Types of Configuration Testing:

1. The client level testing – it has common idea with usability testing[2] and functional testing – the usability and functionality of the system. This type of configuration testing is performed from the perspective of its direct user’s interests.
2. Server level testing – the main goal of this type of check is the inspection of the interaction between the software and the external environment, where it plans to be integrated after the release.

In conclusion it can be said that the configuration testing is not required for each software product, but if it is certainly known that a particular product will be used on different platforms, in different browsers and will support different versions of drivers, then configuration testing[3] will become a necessity for the quality assurance of the software.

Related Posts:

• Regression and Confirmation testing. What is the difference?[4]
• Configuration Management in Software Testing[5]

Source URL: https://blog.qatestlab.com/2015/08/05/why-configuration-testing/

---