We just recently (last week) set up test runner servers and can successfully execute tests on remote machines. Also, I downloaded the latest Test Studio version (151.3.19.0) to my work machine to keep it on the same version as the new test runner servers. But I am running into issues with URL's on remote machines. I have over 100 URL's against which to test and manage them via two worksheets in one excel spreadsheet. I am using data binding to easily switch to a different site. I have bound the first sheet values to the Test Studio script (URL, Userid, and password) and store all others in the second worksheet. This has been working successfully when running test lists locally. However, when I run my test lists remotely, they seem to be hard-wired to one URL, and not the one defined in the first sheet of the excel spreadsheet. I have verified that both the local and remote spreadsheets have the identical bind values in the worksheet. So what is it doing?
Could someone please explain what happens when a test list is run remotely? It takes a while to lauch it, and a long time before it actually begins executing on the remote test runner, so is it compiling the list of scripts and data and shipping the package to the remote machine? I've verified that both the local and remote data is the same, so where is the remote machine getting its execution scripts and data binding from--from the local machine, from the remote machine, or the Scheduler?
The log shows the login script accessing the bind variables. So why is it actually using something else?
Thanks.
Could someone please explain what happens when a test list is run remotely? It takes a while to lauch it, and a long time before it actually begins executing on the remote test runner, so is it compiling the list of scripts and data and shipping the package to the remote machine? I've verified that both the local and remote data is the same, so where is the remote machine getting its execution scripts and data binding from--from the local machine, from the remote machine, or the Scheduler?
The log shows the login script accessing the bind variables. So why is it actually using something else?
Thanks.