Use Looping Patterns Safely in Scenario Editor

Use Looping Patterns Safely in Scenario Editor

Use loops only when repeated behavior is required and bounded. Current Scenario Editor guidance should avoid unbounded legacy Test Designer loop patterns.

Recommended guidance

• Set clear exit conditions for every loop.
• Prefer data-driven iteration or suite configuration when available.
• Protect tests from infinite loops with maximum attempts or timeouts.
• Log enough context to diagnose which iteration failed.

Validation workflow

1. Identify the repeated action and exit condition.
2. Set a safe maximum iteration count.
3. Validate each iteration against expected state.
4. Review output before increasing data size or concurrency.

Last updated: September 20, 2026