Skip to content

Replaying Test Cases

Replay is the validation step between "I configured the test case" and "I'm running it under load." A single virtual user, one pass through the workflow, no production scale. If the replay fails for one user, it will fail for a thousand, only louder. So you replay first, fix what's broken, and only then start the load test.

A successful replay means ASM correlated the dynamic values, authentication worked, and every page returned the status code and content you expected. A failed replay means at least one of those is wrong, and the Errors View tells you which one.

In This Section

  • Running a Replay: How to start a replay, what the different replay modes (Play, Play Fast, Play Slow, Play Next Page, Play Next Element) are for, and how to monitor progress while it runs.
  • Understanding Results: Reading the replay results display. Response time deltas, status codes, validation outcomes, and what "green across the board" actually proves.
  • Debugging Failed Replays: The diagnostic workflow when something fails. 401s, 403s, validation errors, missing variables, and how to use the lineage information ASM emits to find the root cause fast.
  • The Replay View: The live progress panel during replay. Real-time error notifications, extraction status, and validation results as they happen.
  • Troubleshooting: Common replay failures and their fixes, organized by symptom.

The shortest path is run a replay, look at the Errors View, fix the first error, run it again. Don't try to fix everything at once. One error often cascades into the next, so resolving the first usually clears several others automatically.