Skip to main content

​
Run tests

Once a scenario is saved, Qodex can replay it from the web app, a schedule, a webhook, or your CI pipeline. The same test run view collects the result, step output, artifacts, and findings no matter where the run started. This gives teams one place to run smoke checks, nightly regressions, security checks, UI flows, and API suites against staging, production, preview, or any other named environment.

​
How running tests works

The run flow has four parts:
  • Choose a trigger such as manual run, schedule, webhook, or CI.
  • Choose a scope such as one scenario, a test group, a tag-filtered set, failed scenarios, or the full active suite.
  • Choose an environment so the same scenario can run against staging, production, or a preview target.
  • Review results in the test run detail page, with failures classified as real bugs, stale tests, or environment issues.
API scenarios replay as executable scripts. UI scenarios replay through Chromium and Playwright using their recorded steps and cached actions. Repeat runs do not need the agent to regenerate the scenario.

​
Pick how the run starts

From the web app

Start a run manually and watch results stream in the browser.

On a schedule

Run smoke, regression, or security checks on a recurring cadence.

Via webhook

Trigger a run from CI, deploy scripts, or any external system.

​
Pick what runs

Single scenario

Replay one scenario against a chosen environment.

Tag-filtered scenarios

Run every active scenario with tags such as smoke, regression, or security.

Test groups and folders

Run related scenarios as one sequential flow or parallel folder.

Full suite

Run every active scenario and scenario group in the project.

Re-run failed tests

Replay a previous run or isolate scenarios that failed most recently.

In CI

Gate merges and deploys with Qodex runs from your pipeline.

​
What results include

Each run writes to the same test run model:
  • Overall status and per-scenario status.
  • Step-level pass, fail, and skipped results.
  • API request and response evidence.
  • UI screenshots and failure artifacts.
  • Failure classification for broken scenarios.
  • Findings created from confirmed product, security, or environment issues.

​
Where to go next

Run tests from the web app

Start with the easiest manual run path.

Run tests in CI

Add Qodex as a required check in your release workflow.

​
On the roadmap

Skill-typed scheduled runs, SARIF and JUnit XML export, and Slack, email, and webhook delivery of run results are tracked on the Qodex roadmap.