Configuration Testing
Configuration Testing – a special kind of testing to verify the operation of software for various configurations of (alleged platforms supported by drivers with different computer configurations, etc.)
Depending on the type of project configuration testing may have different goals:
- Project on the profiling of the system
The purpose of testing: to determine the optimum configuration of equipment that provides the required performance characteristics, and reaction time test system.
- Project on Migration from one platform to another
The purpose of testing: Check the object of testing for compatibility with the declared in the specification of hardware, operating systems and software products of third parties.
Note: ISTQB Syllabus say nothing about this form of testing as the configuration. According to the glossary, this type of testing is considered there as a test portability:
configuration testing: See portability testing.
portability testing: The process of testing to determine the portability of a software product.
Levels of testing
For client-server applications configuration testing can be divided into two levels (for certain types of applications may be relevant only):
- Server
- Clients
The first (server) level, tested the interaction of produced software with an environment in which it is installed:
- Hardware (type and number of processors, memory, network performance / network adapters, etc.)
- Software (OS, drivers and libraries, third-party software that impacts the application performance, etc.)
The main emphasis here is on testing to determine the optimal hardware configuration that meets the required quality characteristics (efficiency, portability, maintainability, reliability).
At the next (client) level, the software is tested with the position of its end-user and configuration of its workstation. At this stage, will be tested the following characteristics: usability, functionality. To do so would be to hold a series of tests with different configurations of workstations:
- Type, version and bit depth of the operating system (similar type of test is called the cross-platform testing)
- The type and version of Web baruzera, if the tested Web application (for this kind of test is called a cross-browser testing)
- Type and model of video adapter (for testing games is very important)
- Job applications in different screen resolutions
- Versions of drivers, libraries, etc. (For JAVA Applications JAVA version of the machine is very important, too, can be said for. NET applications on version. NET library)
etc.
The order of testing
Before the beginning of the test configuration is recommended:
- create a matrix coating (coating matrix – a table on which are entered all possible configurations)
- conduct prioritization of configurations (in practice, most likely, all of the desired configuration check fails),
- step by step, in accordance with the prioritized, test every configuration.
At an early stage, it becomes obvious that the more requirements for the application for various configurations of workstations, the more tests we need to meet. In this connection, we recommend that, where possible, to automate this process, since it is in the configuration test automation really helps save time and resources. Certainly automated testing is not a panacea, but in this case it would be a very efficient assistant.
We generalize what we have
- configuration is called the compatibility testing of the produced product (software) with different hardware and software
- main objectives – to determine the optimal configuration and testing application compatibility with the desired environment (hardware, OS, etc.)
- Automating the configuration testing to avoid unnecessary expenses.
See Also