Forum Discussion
touch725
14 years agoNew Contributor
I'm working with two workstations on a company intranet. No firewalls. No VM. I suppose I'm not clear on how the firewall / subnet has anything to do with this, since the automated test on the remote workstation is starting fine.
Please follow me here. In the scenario where user does not use distributed testing but is simply running an automated test on the actual workstation the test resides, the test runs fine. Now, if, while that test is running, the user were to lock his screen, wait say a half an hour, unlock his screen, stop the test and view the log, there would be "The object does not exist" errors. This indicates to me that the automated test, when behind the locked screen, is unable to hook into the GUI of the application. I've tested this out and that seems to be a fact.
I then change scenarios and run the test via distributed testing. When I do so, I see the same results as in the first scenario. The task on the immediate workstation starts the test on the remote workstation just fine, as indicated in the previous email, but since the running test is not displayed, again it doesn't seem like the automated test is able to hook into the GUI. Since the test actually started, it would seem that this would eliminate the firewall issue, since, if it were the firewall, the automated test on the remote workstation wouldn't start in the first place. Rather, it is DURING the test run that I'm getting the "The Object does not exist" errors, as indicated in the test log after the test is stopped.
Attached is the .mht log from the test.
Please follow me here. In the scenario where user does not use distributed testing but is simply running an automated test on the actual workstation the test resides, the test runs fine. Now, if, while that test is running, the user were to lock his screen, wait say a half an hour, unlock his screen, stop the test and view the log, there would be "The object does not exist" errors. This indicates to me that the automated test, when behind the locked screen, is unable to hook into the GUI of the application. I've tested this out and that seems to be a fact.
I then change scenarios and run the test via distributed testing. When I do so, I see the same results as in the first scenario. The task on the immediate workstation starts the test on the remote workstation just fine, as indicated in the previous email, but since the running test is not displayed, again it doesn't seem like the automated test is able to hook into the GUI. Since the test actually started, it would seem that this would eliminate the firewall issue, since, if it were the firewall, the automated test on the remote workstation wouldn't start in the first place. Rather, it is DURING the test run that I'm getting the "The Object does not exist" errors, as indicated in the test log after the test is stopped.
Attached is the .mht log from the test.
Related Content
- 2 months agoStoplight
- 12 months agoSiKing
- 2 months agoNicolaFilosa_SE
Recent Discussions
- 4 hours agoSvetaG