Research[1] and literature[2] 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, to understand the behaviour and performance of a software system that uses concurrent computing, particularly assessing the stability of a system or application during normal activity.
Research and study of program concurrency started in the 1950s,[3] with research and study of testing program concurrency appearing in the 1960s.[4] Examples of problems that concurrency testing might expose are incorrect shared memory access and unexpected order sequence of message or thread execution.[5]: 2 [1] Resource contention resolution, scheduling, deadlock avoidance, priority inversion and race conditions are also highlighted.[6]: 745
- ^ a b Cite error: The named reference
wangwas invoked but never defined (see the help page). - ^ Cite error: The named reference
dustinwas invoked but never defined (see the help page). - ^ Cite error: The named reference
pilotwas invoked but never defined (see the help page). - ^ Cite error: The named reference
dijkstrawas invoked but never defined (see the help page). - ^ Cite error: The named reference
britowas invoked but never defined (see the help page). - ^ Cite error: The named reference
binderwas invoked but never defined (see the help page).