Concurrent testing

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, 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. [1]

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
   This article covers testing software reliability under unexpected or rare (stressed) workloads. See also the closely related:
       Scalability testing
       Load testing
       List of software tools for load testing at Load testing#Load_testing_tools
   Stress test for a general discussion
   Black box testing
   Software performance testing
   Scenario analysis
   Simulation
   White box testing
   Technischer Überwachungsverein (TÜV) - product testing and certification
   Concurrency testing using the CHESS model checker
   Jinx automates stress testing by automatically exploring unlikely execution scenarios.
   Stress test (hardware)

References