Product History

The product name Robot was created after Rational purchased SQA TeamTest v6.1. Before that the product was named PLA. This is the reason for references to SQA and PLA within the product. Thus, Robot scripts are in Rational’s SQABasic language, which is based on an early version of Microsoft’s Visual Basic language.

Robot 7.1 was released Feburary, 1999.

Robot 2002.5.20 is our most current release. It has conflicts with McAfee. So uninstall McAfee and re-install it after Robot. Yes. A hassle. The suite version also includes the RobotJ product, which is based on the Java platform.

Product Functionality Summary

Robot automatically plays back scripts that emulate user actions interacting with the GUI of applications under test (AUT). The validity of the AUT is determined by comparators at Verification Points, when objects of the AUT are compared against a baseline of what is expected.

Robot records several types of scripts:

  • SQABasic scripts (using MS-Basic language syntax) capture the commands equivalent to each user action.
  • RobotJ scripts (using Java language syntax) These are compiled into .class files containing java bytecode.
  • Virtual User (VU) scripts (using C language syntax) capture entire streams of conversations HTML, SQL, Tuxedo, CORBA Inter-ORB IIOP, and raw Sockets Jolt protocols sent over the network. These are compiled into dynamic-link library (.dll) files and linked into a .obj compiled from a .c source file which calls the .dll file.
  • Both types of scripts can be initiated from the Test Manager product. VU scripts are executed from a schedule. A separate IBM product, Rational Suite Performance Studio (LoadTest.exe), plays back Virtual User (VU) script commands to determine an application’s performance speed and to detect contention problems caused by multiple users performing actions simultaneously.

Captured scripts typically need to edited to:

  • Add for, while, and do-while loops to simplify repetitive actions.
  • Add conditional branching.
  • Modify think time variables.
  • Respond to runtime errors.
  • Store and retrieve test data to/from datapool files.
  • There are several ways to create Robot scripts. Scripts can read and write to datapools.

As scripts run, Log records are generated into Log Files used to trace script execution conditions.

For more details go to http://www-306.ibm.com/software/awdtools/tester/robot/