loadUI EC2 Agent access
I have a loadUI test case that runs on a local agent - an agent exe started from the command line. I have an ec2 loadUI agent instance instantiated from ami-e220d48b. The loadUI test does not run at a...
Forum Discussion
SmartBear_Suppo
Alumni
AlumniHi,
The WSDL should be cached in the soapUI project file, and thus shouldn't be a problem. We ran the tests you sent us, and from what we can tell, they seem to work (the getSessionId TestCase seems to run fine, verified with Wireshark). I did this using two different desktop computers in our office, one running loadUI and one running the loadUI Agent. In distributed mode I click on "Run Once" on the soapUI Runner, the "Running" count goes to 1 and a few moments later, the "Completed" count increments and "Running" goes back down to 0. What exactly is happening when you try to run it? Specifically what do the counters show in the display on the soapUI Runner? I'll see if I can get access to our EC2 instance to do some more testing later today.
Regards,
Dain
eviware.com
The WSDL should be cached in the soapUI project file, and thus shouldn't be a problem. We ran the tests you sent us, and from what we can tell, they seem to work (the getSessionId TestCase seems to run fine, verified with Wireshark). I did this using two different desktop computers in our office, one running loadUI and one running the loadUI Agent. In distributed mode I click on "Run Once" on the soapUI Runner, the "Running" count goes to 1 and a few moments later, the "Completed" count increments and "Running" goes back down to 0. What exactly is happening when you try to run it? Specifically what do the counters show in the display on the soapUI Runner? I'll see if I can get access to our EC2 instance to do some more testing later today.
Regards,
Dain
eviware.com