Skip to main content

​
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 the scenario detail page and click Run. Choose the environment in the dialog. For UI scenarios, enable video only when you need 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.
  • Final failure classification when the scenario does not pass.

​
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.

Run tag-filtered scenarios

Run a small named set such as smoke or critical.

Re-run failed tests

Replay scenarios from a previous failed run.

Test groups and folders

Run related scenarios as one saved unit.