Have you ever created a test set for an ‘automated’ test execution environment, if yes
Then: When setting up a machine to schedule an unattended, test set execution run, what are some things you should be aware of for this type of environment?
There needs to be some process to start the run. It could be time dependent, some other process starts the automated tool.
IN the days of WinRunner, most tool that started the script had a thread problem. WinRunner could not see objects when it was started by most launchers. I would make sure that what ever is starting the test tool does not interfere with the running of the script.
I always reboot the hosts and make sure they are not locked. I also open an application and browser, just to make sure they open correctly. Granted, I only run on 5 hosts, so if you have a hundred you may wish to run some sort of smoke test prior to executing a large test suite.
Patience is like bread I say.... I ran out of that yesterday.