Record a Scenario Editor Test

Record a Scenario Editor Test

This article replaces legacy Designer 3.0 wording with current Scenario Editor terminology. Use recording as a starting point, then review and maintain the scenario before adding it to a suite.

Recommended workflow

1. Prepare approved test data and a clean application state.
2. Record the shortest flow that proves the target behavior.
3. Review generated steps and replace fragile locators or fixed waits.
4. Add validations and stored values where they prove business behavior.
5. Run a small validation execution and review output before scaling.

Maintenance notes

• Do not keep obsolete Designer-only instructions in current AIQ documentation.
• Prefer clear scenario names and reusable data mappings.
• Use conditional waits instead of arbitrary pauses where possible.

Last updated: September 18, 2026