Configuration Testing

At the modern market of applications and services there are huge number of different operating systems and the so-called. And for each of these supports “cubes” there is a development path, several intermediate versions, and the software manufacturer needs to ensure the compatibility of its product with all their combinations. Testing a site is checking a site in various ways for proper operation. Testing the site is usually used before launching a project in order to obtain guarantees of proper performance or already on an existing project in order to increase its effectiveness. The more complex the site, the more serious testing it needs. Directly, configuration testing itself is conducted in the following way:

  • Identifies various configurations that need to be tested.
  • Configuration data is distributed to the queue by priority, as their number can be huge.
  • In accordance with established priorities, self-testing is conducted.

Configuration management testing gives you confidence that the application will work on different platforms, which means for the maximum number of users. For web applications, usually choose to test for cross-browser. For Windows applications there is testing on various operating systems and bitness (x86, x64). An important component of configuration testing is the test infrastructure: for testing, you need to constantly maintain a fleet of test machines. Their number varies from 5 to several dozen.

Testfort spent a lot of effort and money to create a technical park for configuration and testing of network. Skillfully combining modern virtualization technologies and time-tested methods of working with hardware test stations, Testfort can quickly create the required number of configurations of almost any software or hardware for the configuration testing of customer products. Also, configuration control in software testing often includes checking for compatibility with common system-level software that affects the operation of the entire operating system as a whole. Here, first of all, firewalls, antiviruses and software similar to them, deeply embedded in the OS and changing its behavior are meant.

With the help of configuration tests, the product is checked for compatibility with various software (software) and hardware (hardware) software. As a rule, a software product is made so that it immediately works in the most diverse external environment. If we are talking about a “boxed product”, the compatibility factor becomes even more important in order to find out the reaction of the product to the environment and neighborhood with other software, and conduct these tests. According to the definition of ISTQB, test types are “a means of clearly defining the goal of a specific level for a program or project”. The tester focuses on a specific test goal during the execution of a test case.

The most common type of testing is manual. For example, after updating the configuration, the programmer is forced to check all situations that occur while the user is working in the program, look where errors occur, and correct them. He can spend from several hours to several days, weeks and even months. The duration of the test depends on the configuration itself, and if it is not typical, but changed, then the duration also depends on the complexity of the modifications made to the configuration. Manual testing takes not only a lot of time, but also the strength of specialists. The human factor is also important: the specialist gets tired, distracted, misses some mistakes due to carelessness and also unintentionally introduce new mistakes.

Network configuration testing and correction of base

The mechanism for configuration management in testing and correcting information base built into the configuration itself is one of the simplest types of testing. It is launched from the Configurator mode and serves to diagnose and eliminate erroneous states of information databases that have a different data storage format (file or client-server). The main advantage of component or unit tests is that they are written for the smallest non-trivial functions. This allows you to not only see the places where after some refactoring something could break, but also the principle of operation of the methods covered by tests, since the data is generated separately, you can clearly trace which data entered the method and which we received on output Ideally, even those who have just started to dive into the code should understand the methods when reading the tests written on it.

Test configurations: specifying test platforms

Users are likely to install the application on devices with a wide variety of configurations, for example, with different operating systems, web browsers and other components. You must perform at least some tests in environments with different configurations. A test plan will help you decide which tests to perform in a particular configuration. When performing tests, you must ensure that the necessary configurations are configured for the test environments. The main task of system testing is to check the system as a whole. At the same time, defects are detected, such as incorrect use of system resources, unintended combinations of user-level data, incompatibility with the environment, unintended use scenarios, missing or incorrect functionality, inconvenience of use, etc. To minimize the risks associated with behavior patterns in/or another environment, during testing it is recommended to use the environment as close as possible to the one on which the product will be installed after dispensing.