We are having a problem running some of our automated test cases.
The test case runs fine if you "watch it", but fails if it is not being
watched. The problem happens when someone connects into the test machine,
using remote desktop. When they terminate remote desktop, the machine is
left in sort of a "screen saver" state. (i.e. a user at the local console
would need to sign on, to unlock the console).
If the machine is left in this state then the test cases don't run
correctly. One symptom is that they can't find menu items. Has anyone run
into this before? Any suggestions on how to get around this?
The machines that run our test cases, are locked up in a machine room and
it would be very inconvenient to not use something like remote desktop.