Posted in Information Technology & Systems, Total Reads: 458
Definition: Concurrent Testing
Concurrent testing is a type of software testing that decides the stability of a framework or an application under test. It is the activity of running continuous functionality testing simultaneously keeping in mind the end goal to find defects that would not generally be detected without the extra action. Simultaneous tests regularly put a more prominent emphasis on robustness, execution, and system integration with production like action, which ought to focus right conduct of the framework under ordinary circumstances.
Concurrency testing is also called multi-user testing, performed to recognize the defects in an application when numerous clients login to the application. It helps in distinguishing and measuring the issues in framework parameters, for example, reaction time, throughput, locks/gridlocks or whatever other issues connected with concurrency.
There are 2 levels of concurrency Testing:
Level-1: One application running on top of one application (ex: Receiving an incoming call amid play of music player).
Level-2: One Application running on top of two application (receiving SMS amid voice call when media player is in pause state).
Load runner, one of the widely utilized business performance testing instrument, is utilized for this kind of testing. VuGen (Virtual client generator) is utilized to include various simultaneous clients and the execution of the framework is noted.
When deadlocks are created in printers, it is generally resolved through SPOOLing (Simultaneous Peripherals Operation on Line). It has the de-facto standard for driving the printers.
Now let us describe a situation that give rise to concurrency problem:
In a ticket reservation system let us imagine that there is only one seat available and many users requested for the same place at the same time. To all the users the seat will be shown as available at a particular point of time. Assume two or more users have confirmed the purchase and have given their card details. With the help of RDMS only one is accepted and the others are rejected. So, all confirmations are rejected except one. Supposing if, the credit card transaction for the accepted request is rejected – what happens then? This situation is very common in online purchases, warehouse management, accounting etc. applications. Handling such situations is referred to as concurrency control.