The Configuration Testing is one of the categories under Software Testing. The combinations of Hardware Testing and Software Testing is simply known as Configuration Testing. An application or a system which is tested with random/multiple blending of Hardware and software which result in an application without any flaws.
In this article, we will cover the following topics:
1.Purpose of Configuration Testing.
2.Types of Configuration Testing.
- Software Configuration Testing.
- Hardware Configuration Testing.
- Client Level Testing.
- Server Level Testing.
- Test Cases (sample).
5.Configuration Testing Tool.
PURPOSE OF CONFIGURATION TESTING:
Configuration testing would mainly interact with hardware and is effective than other software testing in fulfilling the application’s configurable requirements.
The defects which were not effectively found by different testing methods can be detected with the configuration testing.
To verify the systems (clients) distributed apart from the server are connected and working effectively.
To verify whether an application was built with less configuration
TYPES OF CONFIGURATION TESTING:
The Configuration Testing is categorized into two types:
- Software Configuration Testing
- Hardware Configuration Testing
SOFTWARE CONFIGURATION TESTING:
The Software Configuration Testing can be done with multiple operating system versions and various browser versions when an Application Under Test (AUT).
The Configuration Testing takes a long time for set up like software installing, software uninstalling and more. It can be considered as time consuming.
The Configuration Testing always begins after the Unit Testing and Integration Testing are complete.
HARDWARE CONFIGURATION TESTING:
In Hardware Configuration Testing, the physical machines were tested with various connections and it can be done only in labs.
When a build is released, the hardware configuration testing is used to check that the application is passing through the physical machines which are connected and are working fine.
The Configuration Testing types:
- Client Level Testing
- Server Level Testing
CLIENT LEVEL TESTING:
In General, the Client Level Testing is based on:
- Usability Testing
- Functionality Testing
This testing can be done only based on Client’s view or user’s point of view.
SERVER LEVEL TESTING:
In Server Level testing, after a release, the communication between the software and external environment are tested to ensure the integration is working fine.
PRE – REQUISITES:
Matrix can be created with the multiple combinations of software and hardware testing.
All the configuration should be tested based on the prioritization.
Its difficult to test all the configuration, so that every configuration must be prioritized.
So, these are the steps to follow for any project to start the Configuration Testing.
An example for configuration testing is that a software system or an application connected to the hardware like money counting machine. In general, there were different models invented for counting machine. Here, let us take the models like Maxsell, StoK, Rolex as an example.
The cash counting machine will be commonly used for banking applications and more.
Let us see some sample test cases for configuration testing using an application connected to money counting machine.
Here, the application and machine have all the combinations of Client Platform, Server Platform and Database.
Client Platform like Windows 7, 8or 10, MAC hardware or macOS operating systems and more.
Server Platform like Windows server platform (server platform 2016), Linux, sever platform (eg.redhat) etc.
Database like MySQL, PostgreSQL, MSSQL, Oracle Database, & Microsoft access etc.
TEST CASES (SAMPLE):
To verify the connection of application with model of the machine is perfect.
To verify the application with model of the machine runs when the prerequisites are installed.
To verify the behaviour of application with model of the machine when prerequisites are NOT installed.
To verify the machine is detects the number mentioning in the system of application.
To verify the application calculates correctly according to the entry.
To verify the machine accepts the count from system of application.
To verify the machine calculates correctly according to the entry.
To verify the counting behaviour of machine that it matches with the actual amount of cash.
These are some sample testcases with the combination of hardware and software as Configuration Testing.
CONFIGURATION TESTING TOOL:
There are many configuration testing tools available currently. The latest tool was released in 2018 and called “SolarWinds”.
The SolarWinds was initially released in 2018 and stabilized in the year of 2019. This is a licensed tool.
This tool is easy to use and understand. The main feature of the tool is to spot the difference between the configurations and can track the changes of application and server.
The advantage of this SolarWind tool is that it reduces the time of troubleshooting and helps in tracking the changes of hardware and software.
Configuration testing is all about the multiple combinations of hardware and software testing. The configuration testing often results in a defect-free application and it takes less time.