Step Procedure

IDE debugger view

This tool has a particular emphasis on the Debugging experience. Here is what a debugger view of a Rundown looks like:

Rundown of all steps

🔍 Let’s zoom into a detailed view of one of these Step reports, which contains complete Request and Response info along with failure information if any:

Step Report

Here are the environment key-value pairs accumulated along the entire execution and appended to the environment from the file and dynamicEnvironment supplied:

Mutable environment after the execution completion

The Step Lifecycle

A Step waterfalls through all these stages and if there is any exception at any stage, the step procedure fails-fast, and ReṼoman captures the Failure in the respective StepReport:

Step Procedure

  • HttpRequestFailure happens if there is an exception while making the request. It is different from HTTP Error response.

  • HTTP Success or Error response is determined by default with HTTP Status Code (SUCCESSFUL: 200 ⇐ statusCode ⇐ 299).

  • HTTP Error response does NOT halt the execution of steps by default.

  • You can configure this behavior using Execution Control

  • If Polling is configured for a step, it is executed after Post-Step Hooks. A PollingFailure is captured in the StepReport if polling fails.

Failure Hierarchy

Here is the failure hierarchy of what can go wrong in this process

Failure Hierarchy

These failures are assertion friendly and provide clear messages with necessary stacktraces to help you troubleshoot.

Each sub-step of the step procedure is timed; see Execution Timing Metrics.