Modifying message-based stubs

You can use either the Test Editor or the Stub Editor to create, modify, and enhance any legacy or new stubs created by HCL OneTest™ API.

For example, you may want to create an advanced message-based stub that can record and report its internal state so that you can create a virtualized application that replicates a complex live transaction processing system.

The following table outlines how to open the Test Editor and the Stub Editor.

If you want to... Do this... Then...
Modify a stub created by GreenHat Tester 5.2.11 (or earlier). In HCL OneTest™ API’s Test Factory perspective:
  • Double-click the stub.
  • Alternatively, right-click the stub and click Open on the shortcut menu.
The selected stub is displayed in the Stub Editor if the stub does not contain any features that cannot be handled by the Stub Editor. Otherwise, the selected stub is displayed in the Test Editor.
Modify a stub created by GreenHat Tester 5.4.0 (or later). In theTest Factory perspective:
  • Double-click the stub.
  • Alternatively, right-click the stub and click Open on the shortcut menu.
The selected stub is displayed in the Stub Editor.
Note: You can also modify a stub while it is running. For information about this, refer to Modifying running stubs.
Use Test Editor to modify a stub created by any release of HCL OneTest™ API. In the Test Factory perspective, right-click the stub and click Open With > Test Editor on the shortcut menu. The selected stub is displayed in the Test Editor.

The Stub Editor comprises the following tabs:

The following topics describe how to use these tabs.

Note: For information about using the Test Editor, refer to HCL OneTest™ API reference.
Note: For information about debugging message-based stubs, refer to Debugging message-based stubs.
Feedback