To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at

If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

Software Testing

Software Testing

Aug 21 2013

Software testing is an investigation of a software product with the intent of finding software bugs and verifying that the program works as expected. This investigation is based on test suites chosen according to certain parameters and specifics of software. In a wider sense, software testing is software quality assurance technique comprising test design, test execution and analysis of test results.

Contemporary software products usually have to be developed in very short terms and at limited project budgets. Programming today is rather craft than art for millions of programmers. Such haste, unfortunately, makes them ignore the necessity of software security assurance, thus exposing end users to undue risk. Software quality control is a considerable aspect of the software development process, for it helps provide security, reliability and usability of the product. There exist multiple approaches to and techniques of software testing nowadays. However, efficient testing of complex software systems is rather a creative process than formal compliance with strict, definite rules.

Testing Levels

Unit testing is a software testing level at which the smallest parts of software are tested, for example individual classes or functions. Unit testing is often performed by software developers themselves.


Integration testing is a software testing level at which interfaces between components or subsystems of software are tested.


System testing is a software testing level at which a complete integrated system is tested to evaluate the system's compliance with its specified requirements. System testing includes alpha testing and beta testing subcategories.


Classification of Testing Types

All the testing types are classified into several categories according to a number of criteria. The following are the most common ones.

By the Object under Test

Functional testing is a software testing type intended to validate that the program complies with functional requirements. Functional testing checks if a software product can correctly solve certain tasks as required by users.


Performance testing is a software testing type performed to determine how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are executed before and after program optimization in order to find out any changes of performance. If an optimization leads to a performance drop and therefore is unsuccessful, the programmer may refuse using it. In case of a performance gain, its degree is compared to the anticipated one to make sure that the optimization has been done successfully. The purpose of performance testing is to find out any cases of performance increase and decrease in order to avoid faulty modifications.


Load testing is a software testing type performed to determine a system's behavior under normal, increased, and anticipated peak load conditions. Being performed before the commercial exploitation of the system, load testing helps assure that no sudden performance losses will occur later (in about a year), when the system is loaded with data.


Stress testing is a software testing type that determines robustness of software beyond the limits of normal operation, i.e. under stress conditions like large input data amounts, disk space shortage or execution on a low-performance processor.

Stress testing is also performed on a customized solution and server group to evaluate its ability to serve many users at a time. It is not only the server group which is checked by stress tests but also the influence of software customization on the system performance in general and its fault-tolerance. This testing type requires a network of several computers emulating activity of a group of users.


Stability/endurance/soak testing is a software testing type that determines stability of software during a long testing time under medium (anticipated) workload.


Wikipedia. Software Reliability Testing.

Security testing is a software testing type that evaluates the ability of software security mechanisms to react to system intrusions.


Compatibility testing is a software testing type that evaluates the application's compatibility with a certain computing environment.


By the Depth of Knowledge of the System

Black-box testing is a software testing type performed on a software system which can only be accessed through user interfaces or external interfaces which allow another computer or process to connect to the system to run tests on it. This technique is still the most popular in everyday testing practice, but it has a lot of drawbacks. For instance, some errors can only occur in specific conditions and therefore are difficult to find and reproduce.


White-box testing is a software testing type when the tester has a free access to the source code of an application and can write test codes covering the libraries it uses. White-box testing includes methods of code review and software inspection. This methodology allows peeping into the "black box" to focus on the application's internal implementation which determines its behavior. The main problem with this methodology is that run-time computations are difficult to monitor. White-box tests evaluate the program's logic, so testing is said to be complete when it tracks all the possible code paths. Even a program of medium complexity may have dozens of thousands of code paths.


By the Product Maturity Phase at Which Testing is Performed

Alpha testing is a software testing type implying simulated or actual operational testing (by developers or end users correspondingly).


Beta testing is a software testing type when limited versions of software are released to a group of people so that further testing can ensure the product has few faults or bugs.


Regression testing is a software testing type performed to ensure that no previously found bugs have come back after any code modifications and bug fixes, as well as to determine the main functionality of the software product. This type of testing is usually performed on every new product version. It is the most important testing phase immediately before the end of the development process, for it is extremely crucial to make sure before the release that not only the main functions work properly but also that no previously detected bugs have been brought into the final version. Being an integral part of functional testing, regression testing guarantees that no modifications brought into the code by bug fixes have caused negative influence on all the other functions of the application.


Smoke testing is a software testing type performed as a set of tests to ensure that the product can be launched successfully. If no errors occur during the launch, the smoke test is said to be passed. If the smoke test is failed, software is sent back to the developer team for revision. The point is that sometimes different components of a program are written by different developer teams and may often appear non-compatible when being assembled into a whole, which makes it pointless to test the product in general.


By the Automation Criterion

Manual testing is a software testing type when no software tools are used to run tests and analyze test results. Instead, it is done manually by the tester.


Automated testing is a software testing type when software tools are used to perform tests and analyze test results. Naturally, automated testing is highly useful, as it allows saving time and resources.

It often happens during the development process that new versions with bug fixes are released every day or even several times a day. Smoke tests should be automated first of all because we need to check as soon as possible after every build of a new version that the program can be successfully launched. Automated tests can be completed in just a few seconds, so you can quickly conclude if the build is successful. Being performed by a human tester, the test will take him much more time. Thus, smoke testing automation is an opportunity for the testing department to save incredibly much time.

There exist a number of applications providing test automation features. The most popular are HP LoadRunner, HP QuickTest Professional, HP Quality Center, and TestComplete.

Automation in general does not only helps save development time but also improves security and reliability of software products. Testers will also see significant advantages of this technique: reliability of the testing process and results improves, testing time decreases, and the tester's work gets less stressful. Automated testing will never replace human of course, but it indeed can simplify the software testing engineer's work.


Dynamic and Static Code Analysis

As a software product is passing later development phases, the cost of bug elimination may grow exponentially. Static and dynamic analysis tools can help prevent these expenses due to earlier detection of software bugs.

Run-time analysis (dynamic analysis) is a software testing type performed when executing the program. Dynamic analysis reveals defects in the source code as they are occurring. The analysis process can be divided into a number of steps: preparing input data, running a test program launch, gathering the necessary parameters, and analyzing the output data.


Static analysis is a software testing type performed without actual execution of the program. Static analysis enables quick detection of bugs in the source code before it can be executed.

In practice, developers may use both analysis techniques to speed up the development process and testing process, as well as improve the quality of the software product.


Popular related articles
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →