Search

Mapping Extensions

Once an Extension is created, it must be mapped to a test action, test case, or orchestration  before it can be used. Extensions can be mapped at different points of execution and can be configured directly in Architect, on the Test Detail page, or in Slider View.

Mapping Types

There are two types of Extension mappings. Both may be applied to the same action:

  • Pre-hook
    Executes before the action runs.
    • Use this when you want to override input values or modify runtime data before the step executes.
  • Post-hook
    Executes after the action, test case, or orchestration runs.
    • Use this when you want to capture or process data that appears dynamically (e.g., randomly generated IDs, response values, or new elements rendered after the step). 

Mapping Extensions with Architect

  1. Launch Architect to create a new test.
  2. Click the blue + icon.
  3. Select Extensions.
  4. Choose the action by clicking its white circle icon.
  5. In the Architect Extensions sidebar, select the desired Extension from the Pre-hook and/or Post-hook dropdown.
  6. Click Add.
  7. Continue recording your test.
  8. Click Save when complete.

Result: Once saved, the Test Detail page will display the Extension mapping in the Action footer.

Mapping Extensions on the Test Detail Page

  1. Expand the action that requires the Extension.
  2. Click Manage Extension.
  3. For Pre-hook and/or Post-hook, click the corresponding Manage Extension button.
  4. Select the Extension (use the Search feature if needed).
  5. Click Save.

Result: The mapped Extension will appear in the Action footer.

Mapping Extensions in Slider View

  1. Open the test case in Slider View.
  2. Select the action that requires the Extension and click the gear icon.
  3. Click Manage Extension.
  4. For Pre-hook and/or Post-hook, click the corresponding Manage Extension button.
  5. Select the Extension (use the Search feature if needed).
  6. Click Save.

Result: The mapped Extension will appear in the Action footer.

Deleting a Mapped Extension

You can remove a mapped Extension from either the Test Detail page or Slider View. Removing an extension from a test action, test case, or orchestration will not delete it from the extension library.

On the Test Detail Page

  1. Expand the action with the mapped Extension.
  2. Click Manage Extension or click directly on the Mapped Extension.
  3. In the Pre-hook and/or Post-hook section, click the X to remove the mapping.
  4. Click Save.

Result: The Extension will be removed from the Action footer.

In Slider View

  1. Select the action with the mapped Extension and click the gear icon.
  2. Click Manage Extension or click directly on the Mapped Extension.
  3. In the Pre-hook and/or Post-hook section, click the X to remove the mapping.
  4. Click Save.

Result: The Extension will be removed from the Action footer.

Best Practices

  • Use Pre-hooks for input overrides or test data injection.
  • Use Post-hooks for result collection, logging, or chaining data between steps.
  • Keep Extension mappings consistent across tests by documenting where and why they’re applied.
  • Periodically review Extension mappings to ensure they remain relevant and efficient.
  • Replace an extension by simply editing the test step and selecting a different extension, then saving your changes.