Customer Service Center

iTest supports multi-threaded execution: Run tests (of the same session type) in parallel without conflict.

A lock step specifies a lock name, and all steps that are indented as children of the lock step are locked (often referred to as mutex or semaphore). The named lock is released for use by other lock steps when execution finishes for the currently locked steps. A lock is useful in the following situations:

• When you need to ensure that no steps in a separate section of a test case or procedure alter a variable while a particular set of steps is working with it
• To ensure that all steps in a procedure that opens a session, performs actions in the session, and finally closes the session can execute atomically -- that is, with no steps in other threads changing something about the session

Course: New in iTest 4.0
Run Time: 2 min
Tags: iTest, multi-threaded, Synchronization