Lecture
Configuration Testing ( Configuration Testing ) is a special type of testing aimed at checking the software operation under various system configurations (the stated platforms, supported drivers, various computer configurations, etc.)
Depending on the type of project, configuration testing may have different goals:
System Profiling Project
The purpose of testing : to determine the optimal configuration of the equipment, providing the required performance characteristics and reaction time of the system under test.
Project on system migration from one platform to another
Purpose of Testing : Check the object of testing for compatibility with the equipment, operating systems and third-party software products declared in the specification.
Note : In ISTQB Syllabus does not at all talk about this type of testing as configuration. According to the glossary, this type of testing is considered there as testing portability:
configuration testing: See portability testing .
portability of the software product.
For client-server applications, configuration testing can be conditionally divided into two levels (for some types of applications, only one can be relevant):
At the first (server) level, the interaction of the released software with the environment in which it will be installed is tested:
The main focus here is on testing to determine the optimal configuration of the equipment that meets the required quality characteristics (efficiency, portability, maintainability, reliability).
At the next (client) level, the software is tested from the perspective of its end user and the configuration of its workstation. At this stage, the following characteristics will be tested: usability, functionality. To do this, you will need to conduct a series of tests with different configurations of workstations:
etc.
Before starting the configuration test it is recommended:
Already at the initial stage, it becomes obvious that the greater the requirements for the operation of the application with different configurations of workstations, the more tests we will need to conduct. In this regard, we recommend, if possible, automate this process, since it is during configuration testing that automation really helps save time and resources. Of course, automated testing is not a panacea, but in this case it will be a very effective helper.
Comments
To leave a comment
Quality Assurance
Terms: Quality Assurance