Remote Agent is used to integrate TestOptimal with your 3rd party automation tools. It operates on the plain http, as long as the external tool can send and receive http requests, you can integrate it with TestOptimal. This covers pretty much any tools on the market.

Below are a few examples of remote agents you can create to extend TestOptimal to test your application using your existing test automation framework like QTP, Rational Robot and Functional Tester, TestComplete and SilkTest, etc. The remote agent must implement the API to communicate with TestOptimal server as described in RemoteTriggerPlugin and RemoteCommandPlugin.

Refer to Agent Integration Process for details on how to develop an integrated remote agent with TestOptimal.

• Remote Agent in Java - for interfacing with other test automation tool that supports java like IBM Rational Robot, Functional Tester, and Borland SilkTest. See javadoc.
• Remote Agent in VBA - for interfacing with other test automation tool that supports VBA.
• Remote Agent in VBS - for QTP, Mercury QualityCenter, TestComplete.
• Remote Agent in AutoIt - for open source automation tool AutoIt.

You may also start the model execution remotely from the agent. The following are the url requests for starting model executions in the remote agent:

• http://localhost:8888/MbtSvr/app=client&action=exec&userid=xxx&password=yyy&model=myModel - starts the execution on model myModel.
• http://localhost:8888/MbtSvr/app=client&action=exec&userid=xxx&password=yyy&model=myModel&mbtMode=OptimalSequencer - starts myModel execution using sequencer OptimalSequencer
• http://localhost:8888/MbtSvr/app=client&action=exec&userid=xxx&password=yyy&model=myModel&mbtMode=mCaseOptimal&mCase=zzz - starts myModel execution to run mCase zzz.

If you are using java agent, you can remote start the model with execModel(userID, password, mbtMode, mCase).