Sunday, March 16, 2014

Setting up Robotium Remote Control

Robotium Remote Control includes the following components


  • Robotium Test Runner
  • SAFS TCP Messenger
  • SoloRemoteControl
Rebotium Test Runner :
The TestRunner is a general-purpose InstrumentationTestRunner created specifically for Robotium/Solo Remote Control.  Because the actual AUT-specific test code is on the remote Controller and NOT in the TestRunner, the TestRunner may easily be resigned and repackaged for testing any number of AUTs without modifying its internal code.  The TestRunner receives its remote command and control data and reports its success, failure, and results data through the Messenger service.the TestRunner may easily be resigned and repackaged for testing any number of AUTs without modifying its internal code.  The TestRunner receives its remote command and control data and reports its success, failure, and results data through the Messenger service.

SAFS TCP messenger:
TCP messenger is a general-purpose SAFS TCP Communication service on Android.  It allows us to provide remote control capabilities over TCP even for AUTs and TestRunners that DO NOT have the required INTERNET permissions necessary for TCP communications.  This service is required (and provided) for Robotium Remote Control even for AUTs that might already have INTERNET permissions.

Prerequisites for Setting up Robotium RC:

  • Android SDK
  • APachec Ant
  • Remote Robotium Libraries

No comments:

Post a Comment