Jump to content

Concurrent testing

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 111.93.20.138 (talk) at 13:27, 13 July 2015 (Undid revision 671251801 by 111.93.20.138 (talk)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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

References