Data-Drive Wait Values in Scenario Editor

Data-Drive Wait Values in Scenario Editor

Use data-driven wait values only when different test data genuinely requires different timing. Prefer conditional waits based on application state whenever possible.

When data-driven waits make sense

• Different workflows have documented processing windows.
• External systems return at different approved polling intervals.
• The timing value is part of the test data model and needs traceability.

Good practices

1. Store timing values in an approved DPL or test data source.
2. Use clear field names such as waitTimeoutSeconds or pollingIntervalSeconds.
3. Set maximum limits so bad data does not create excessive waits.
4. Review repeated wait failures before increasing data-driven timing values.

Last updated: September 9, 2026