Concurrent testing

Research and literature on Concurrency testing and Concurrent testing typically focuses on testing software and systems that use Concurrent computing. The purpose is, as with most software testing, is to understand the behaviour and performance of a software system that uses concurrent computing.

Concurrent testing is a software testing activity that determines the stability of a system or application under test during normal activity. Concurrent testing is the exercise of running continuous testing with functional testing concurrently in order to discover defects that would not otherwise be detected without the additional activity. Concurrent tests commonly put a greater emphasis on robustness, performance, and system integration with production-like activity, which should determine correct behavior of the system under normal circumstances.

Concurrent test vs. Stress test;

Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it (in which case it is sometimes called negative testing). The main purpose of this process is to make sure that the system fails and recovers gracefully—a quality known as recoverability.

Concurrent testing implies a controlled environment staying at a constant level of activity. Stress testing focuses on more random events, chaos and unpredictability.

See also

• Software testing
• Scalability testing
• Load testing
• Software performance testing
• Scenario analysis
• Simulation
• Stress test (hardware)
• System testing

General References

• What is Concurrent Testing? at the Wayback Machine (archived 19 August 2016)
• Concurrent Software Testing: A Systematic Review at the Wayback Machine (archived 24 September 2015)