Description Paul Slauenwhite 2007-05-03 10:56:58 EDT

The test execution harness does not limit the maximum time allowed for operations.  For example, when executing a test, the test execution harness executes blocks of code with a limit to the amount of time to execute the block of code.  As a result, the user is not made aware of stalled operations.  Instead, stalled operations appear as a hang of the test execution.  The user should be made aware of stalled operations after a period of time so they can manually cancel the test execution.

For instance:

block A
check if user clicked cancel
block B
check if user clicked cancel
block C
.
.
.

We should have a time-out for each of these blocks, and inform the user what
possible things have gone wrong and what steps they can take to resolve it.