​

Run a single scenario

Run a single scenario when you want to check one flow, debug one failure, or verify a scenario before adding it to a larger suite. The run uses the same execution path as scheduled, webhook, and CI runs, so the result shape is consistent everywhere. If several scenarios need to run together, use a test group or folder instead of starting each scenario one by one.

​

Before you start

You need:

• One active scenario.
• A configured environment.
• Any variables, auth profiles, or test data the scenario references.

API scenarios need compiled script content. UI scenarios need recorded browser steps.

​

Run the scenario

Open Test > Scenarios and choose the environment in the selector at the top of the page. Then hover the scenario row and click Run, or open the scenario and click Run. For UI scenarios, click Record instead only when you need a video for a shareable reproduction. Screenshots and failure artifacts are still captured without video.

​

Watch the replay

Qodex opens a new test run page for the scenario. As it executes, you can review:

• Step status and assertion text.
• API request and response evidence.
• UI screenshots and failure artifacts.
• Script stdout and stderr.
• A label saying what the failure was when the scenario does not pass, such as Functional regression or Test needs repair.

From the result, Ask in chat opens a chat that answers questions about what the scenario returned, and Fix in chat opens a chat that repairs a failing scenario.

​

Why single-scenario runs are useful

• Confirm a new scenario works before marking it active.
• Reproduce a failed scenario without running the full suite.
• Test the same scenario against a different environment.
• Check whether a stale test is fixed after editing a selector or assertion.
• Capture fresh artifacts for a bug or finding.

​

Related