Open GoogleCodeExporter opened 9 years ago
FEST tests are executed in a serial manner on purpose. The reason being is that
there
is only one mouse and one keyboard per computer that cannot be shared
simultaneously
between two or more tests (e.g. both tests have their own dialogs and they need
to
move the mouse or enter text at the same time.)
I'm going to mark this bug as a "invalid issue". Please feel free to change its
status to "new" if you consider something else can be done.
Original comment by Alex.Rui...@gmail.com
on 29 Mar 2008 at 1:52
Maybe I am misunderstanding, but I thought the purpose of the screen lock was
to
queue the tests and make them run in series, even if they are on different
threads.
In other words, the second test is forced to wait until the first test
completes,
and then the second test can acquire the lock and run.
This is not what is happening. One of the tests runs but the other does not.
The
entire Ant build deadlocks and the process has to be killed. I am assuming
that the
first test is not properly releasing the lock. When is the lock supposed to be
released? When cleanUp() is called?
Original comment by british...@gmail.com
on 29 Mar 2008 at 2:04
Hi Dan,
The screen lock is released when cleanUp(). I'm going to reopen this bug and
investigate further, reproducing the scenario you described.
Thanks,
-Yvonne
Original comment by wanghy1...@gmail.com
on 31 Mar 2008 at 2:51
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
Issue migrated to http://jira.codehaus.org/browse/FEST-23
Original comment by Alex.Rui...@gmail.com
on 2 Mar 2009 at 7:58
Original issue reported on code.google.com by
british...@gmail.com
on 29 Mar 2008 at 12:41