Extending the generic test recorder

A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions. Developing a test recorder entails adding the Generic Recorder extension point to the Generic Recorder Framework (GRF), and extending the recorder user interface wizard and the four main GRF helper classes.

Understanding the GRF and GRF helper classes , functioning recorders , the user interface wizard , and the Agent Controller is essential for creating your own test recorder. The GRF is part of the Test and Performance Tools Platform (TPTP). The recorder runs on the Agent Controller and produces a recording file.

• Generic Recorder Framework
  The Generic Recorder Framework (GRF) provides a common user interface experience for all users that record tests. The GRF simplifies the process of extending a recorder by including a reusable extension point. For example, you could define one custom set of wizard pages to reuse for multiple recorders.
• Test recorders
  A test recorder captures user interactions with an application. These interactions are saved, and a test is generated from these recorded actions.
• Recorder user interface wizard
  The recorder user interface wizard records a session with a Web application, generates a test from the recording, and then opens the test in the test editor.
• Creating a new test recorder
  To create a test recorder, you extend the recorder user interface wizard and the four main Generic Recorder Framework (GRF) helper classes in the extension point org.eclipse.hyades.test.core.Recorder.
• Example of a new test recorder
  The following example shows how the Generic Recorder extension point might be defined for the URL recorder in the plugin.xml file of the org.eclipse.hyades.test.tools.ui plug-in.
• Porting a recorder into version 4.2 from an earlier version
  Recorders that were created in earlier versions of the Test and Performance Tools Platform (TPTP) will still work in version 4.2. However, they cannot take advantage of the new auto-deployment feature. Without making changes, old recorders must still manually deploy recorder JARs to the Agent Controller and cannot use the recorder UI wizard entry point.