Test Completion With Running Processes

[Scott Lowrey]

I've noticed a discrepancy in the behavior between running tests on the 
command line and running them via the GUI.

Scenario:

Test code spawns several subprocesses.  Exception occurs while executing 
test code.  Bug in the test class (mine) leaves one process outstanding.

Result:

If this test is run via the command line ('qmtest run'), the exception 
is properly noted and the test ends with an ERROR result.  The 
outstanding process remains as an orphan.

If this test is run via the GUI, the browser loops waiting for the test 
to end.

Obviously, QMTest is waiting for all processes associated with it to end 
before declaring the test complete.  That is a Good Thing, I think.  But 
why does the command-line test come back as soon as the exception 
occurs, in spite of the outstanding process?

-- 
*Scott Lowrey*
NexTone Communications
Germantown, Maryland

/(240)912-1369/
www.nextone.com <http://www.nextone.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sourcerytools.com/pipermail/qmtest/attachments/20040126/9d8e157d/attachment.html>