​

Run tests from the web app

The web app is the fastest way to run Qodex scenarios by hand. Use it when you want to check a new scenario, run a smoke set after a deploy, or inspect failures without leaving the product. You can run one scenario, selected rows, a filtered set, or the full active suite. Every run writes to the same test run history.

​

Before you start

Make sure the project has:

• At least one runnable scenario.
• An environment such as staging, prod, or preview.
• Any variables, base URLs, and auth profiles required by the selected scenarios.

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

​

Pick the environment

Open Test > Scenarios. The environment selector at the top of the page decides where every run you start from this page goes. It lists the project’s own environments and starts on the default one.

​

Run one scenario

Hover a scenario row and click Run, or open the scenario and click Run. For UI scenarios, click Record instead when you need a video of the browser session for a shareable reproduction.

​

Run a filtered set

Use the State, Last run, Severity, and Tags filters or the search box to narrow the list. Then click Run all. Qodex runs the full filtered result set, not just the rows visible on the current page. This is useful for tags such as smoke, critical, security, or regression.

​

Run selected rows

Tick the scenarios you want, then click Run selected. Use this when the set is ad hoc and does not deserve a permanent tag. When every selected scenario is a UI scenario, Record selected runs them and records a video of each.

​

Run a group or folder

Switch the toggle at the top of the page to Groups when related scenarios should run together. Click Run group to start the whole group against the selected environment. Sequential groups run members in order. Parallel groups run members independently at the same time. UI-only groups also show Record, which captures video for each UI scenario in the group.

​

Watch the run

After you start the run, Qodex creates a test run and opens the run detail page. As scenarios execute, you can see:

• Step status and assertion text.
• API request and response evidence. Use the copy buttons to copy a request or response, and Show full response when a body was cut short.
• UI screenshots and failure artifacts.
• Live stdout and stderr for script execution.
• Passed, failed, and skipped counts.
• A label on each failure, such as Functional regression, Vulnerability present, or Test needs repair.
• Findings created by failed scenarios.

You can leave the page and come back later; the run continues in the background. All runs are listed under Test > Test runs.

​

Ask about a result

Select a result and click Ask in chat to open a new chat about what it returned, for example “which records came back without an email address”. The chat answers from what the run stored, so it works on large responses without calling your API or opening the app again. For a failing result, Fix in chat opens a chat that repairs the scenario instead.

​

Read-only environments

If the selected environment is read-only, or has destructive tests turned off, scenarios tagged destructive are skipped instead of run. They show as skipped with the reason, and the run reads SKIPPED rather than PASSED. See Sensitive endpoints.

​

Draft behavior

Scheduled runs skip draft scenarios. Manual runs from the web app honor your explicit selection, so drafts can run when you choose them directly.

​

Related