Classification of software testing types

Searching for bugs in software products differs depending on the end goal. The algorithm for identifying defects in the site when translating a page into a foreign language and determining the limit load will differ in methods, tools, and specialists involved in the process. In this article, we are going to review the main types of testing classified on different criteria and help you to choose professional web application testing services that are right for your product.

1. The purpose 

Every software product has to fulfill one or several key tasks. From an application with geo-maps, we expect accurate orientation in space, from an online store site – the correct search for goods according to specified parameters, etc. But we can also test those same software products from a design standpoint.

Thus, analysis of software from the viewpoint of its key or additional functions defines the type of testing:

• Functional
• Non-functional

Functional testing is aimed at checking which functions of the software are implemented and how well they are implemented.

Non-functional – testing the correctness of non-functional requirements. It evaluates how the software product works.

This kind of testing includes the following types:

• Performance testing – operation of the software under a certain load.
• User interface testing – user-friendliness in interaction with different interface parameters (buttons, colors, alignment, etc.).
• UX testing – the correctness of the logic of using the software product.
• Security testing – defining software security: whether it is protected from hacker attacks, unauthorized access to data, etc.
• Installation testing – evaluation of the probability of problems that may occur when installing, uninstalling, or upgrading software.
• Compatibility testing – testing of how the software works in a specific environment.
• Reliability testing – the program’s operation testing under a long average expected load.
• Localization testing – assessment of the correctness of the software product version (linguistic and cultural aspects).

2. Automatization level

• Manual – without the use of additional software tools, i.e., “by hand.”
• Automated testing – with the use of software tools.

3. The scenario positivity

This approach defines the behavior of the system under habitual and extreme conditions.

• Positive testing is an evaluation of the expected behavior. This testing is conducted in the first place because it determines the correctness of the program operation.
• Negative – determination of the system stability in a non-standard situation. For example, an unexpected scenario of user interaction with the interface.

These types of testing are often performed simultaneously. After all, when working on some functionality, it is easier for a tester to evaluate its behavior in both standard and non-standard conditions.

4. Access to the software code

During the testing process, an engineer can work with the software without accessing its code and can determine the correctness of the work by looking at the code.

By access to the code of the software product, testing is divided into:

• White-box testing – with access to the code.
• Black-box testing – without access to the code.
• Grey box testing – based on limited knowledge of the internal structure of the software. They often say that this is a mixture of “white-box” and “black-box” testing, but it’s fundamentally wrong. In this case, the tester does not work with the code of the software product, but he is familiar with the internal structure of the program and the interaction between the components.

5. The level

This point defines the testing object.

• Modular/unit testing – verification of the correctness of the work of separate software units, and modules. This type of testing can be performed by developers themselves.
• Integration testing: A test of an interaction between several software units.
• System testing – verification of an application in general.
• Acceptance testing – assessment of compliance of a software product to specified requirements.

Transition to each new step is a movement from microlevel to macrolevel. This is an important stage of testing, because error-free written modules may simply not work together.

Finding a trustworthy QA specialist is a tough task, so a good idea would be to hire a QA developer team from a specialized company.

Share on Facebook

Tweet

Follow us