Validation and Store Content in Scenario Editor

Validation and Store Content in Scenario Editor
Use validation and stored content when a Scenario Editor test needs to capture a value from the application and compare it later in the same scenario or execution. This keeps the test focused on business behavior instead of fixed screen text.
Common uses
Capture an order number, account value, token, or confirmation message.
Validate that a value displayed later matches the value generated earlier.
Store a dynamic value for a downstream step in the same test flow.
Recommended workflow
Identify the stable element or response value to capture.
Store the value with a clear name that describes its business meaning.
Use the stored value in a later validation step.
Run a short validation execution before adding the pattern to a larger suite.
Last updated: September 18, 2026