Hallo,
recently I started testing on a remote machine but still my scripts do not run. My application is started so the connection to the agent on the remote machine seems to be OK.
My remote script looks as follows:
Public Module Main Dim _desktop As Desktop = Agent.Desktop Public Sub Main() Agent.Connect("192.168.1.21") _desktop.PushButton("Anmelden").Select() _desktop.TextField("TextField").SetPosition(New TextPosition(0, 0)) _desktop.TextField("TextField").SetText("adm") _desktop.TextField("TextField").TypeKeys("<Enter>") _desktop.TextField("TextField").SetText("") _desktop.TextField("TextField").SetText("sicas,S8") _desktop.TextField("TextField").TypeKeys("<Enter>")
and so on. I'v recorded it on the remote machine and it's running when I execute it locally on the remote machine.
I call the remote script in the following way:
Agent.Connect("192.168.1.21") Workbench.RunScript("TF792_1")
This is the error message I get:
Any help is appreciated.
Best regards - Ulrich Bangert
hi ulrich (nice name btw ;),
the workbench does not explicitely support remote agents as of now. this means that there will be some limitations. you can still use Agent.Connect to connect to a remote machine, but in subsequent find operations you will have to use raw locators instead of object map entries as the remote agent you are connected to does not know anything about the local object map.
if you replace your object map entries with the corresponding locators you should however still be able to run your tests against a remote machine.
kind regards,
ulrich
HI Ulrich K
I was investigating this issue just as you replied :) I had set up two instances of ST WB to use a single database repository thinking that both machines could access the Object Maps. However this does not appear to be the case, is this as designed?
Thanks
John
Hi John,
this is as designed. the problem with object maps is, that the local workbench sends the object map contents to the local agent, when the test starts. the remote agent does not get the object maps and therefore the lookup doesn't work.
the remote workbench instance does not do do anything in that scenario so it doesn't matter whether you have a second instance on the remote machine running.