WR 7.5 / TD 7.6 client timeout issues
Has anyone run into the problem of the WinRunner session timing out? We have just upgraded to TD 7.6 and admin has a short client timeout value (1 hour). So if the lab machines sit idle for over an hour, we get this nifty error stating that the session has timed out and our scripts won't run. Also having a difficult time with the admin increasing (or eliminating) the client timeout session.
Any info, suggestions would be appreciated.
Re: WR 7.5 / TD 7.6 client timeout issues
You can download a "test set scheduler" or so from Mercury support site. With this you can let the Windows scheduler start your TestDirector testset. No TD connection is open before and can get disconnected.
But i have not much luck with running overnight tests. A lot of things are going wrong so i start my tests on a second machine early in the morning before the developers appear.