Create a Run

Create a Run lets you execute any combination of test cases on-demand. Pick individual tests, select entire folders, or reuse a previous run’s test selection - all from a single dialog.

​

The Runs Page

The Runs page is the central hub for all test executions. It has three tabs: The Grouped Runs tab shows summary stats at the top: total runs, passed, failed, and average duration. Each row in the table displays the run name, config count, start time, trigger type (Manual or Scheduled), environment, duration, and pass/fail counts. Click ”+ Create Run” in the top-right corner to open the Create Run dialog.

​

Run Configs Tab

The Run Configs tab in the Runs page is where reusable execution profiles are managed.

• Create named configs for browser + viewport combinations
• Set locale and timezone defaults per config
• Reuse the same config across test cases, test plans, and ad-hoc runs

​

Create Run Dialog

The Create Run dialog lets you configure and launch a new run.

​

Run Settings

At the top of the dialog, configure the basic run settings:

​

Selecting Test Cases

Below the run settings is the Select Test Cases section. A toggle switches between two selection modes:

• Test Explorer - Browse your folder structure and pick tests
• Grouped Runs - Pick tests from previous runs

​

Test Explorer Mode

Test Explorer shows your test cases organized in the same folder structure you use in the Tests section. You can:

• Expand folders to see nested test cases
• Search by test title using the search bar
• Filter by tags using the Filter button
• Select individual tests using checkboxes
• Select entire folders to include all tests within them

This mode is useful when you know exactly which tests you want to run, or when you want to run all tests under a specific folder.

​

Grouped Runs Mode

Grouped Runs mode lists all your previous runs - both manually created runs and scheduled test plan runs. Each entry shows:

• Run name and timestamp
• Trigger type (Manual / Scheduled)
• Environment badge
• Pass/fail counts with color indicators

Expand any run to see its individual test cases. Each test case shows its last result (pass/fail icon). From here you can use the quick selection buttons: You can also select individual test cases manually, and even select tests across multiple previous runs.

​

Launching the Run

Once you’ve selected your tests, the “Create Run” button shows the total count of selected tests (e.g., “Create Run (46)”). Click it to start execution. Tests are queued immediately and begin running in parallel based on your available workers. If you selected run configs, Supatest expands execution into a matrix:

• selected test cases
• selected run configs
• browsers in each run config
• viewports in each run config
• enabled scenario rows (for table-driven tests)

This means a single Create Run action can generate multiple concrete runs per test case.

​

Run Details

Click any row in the Grouped Runs table to open the run details page. The run details page shows:

​

Summary Cards

Five cards at the top provide an at-a-glance overview:

​

Test Runs Tab

The default tab lists every test case in the run with sortable columns: test case name, status, trigger, environment, start time, and duration. When a test executes as multiple runtime entries (for example from multiple run configs, browsers, viewports, or scenario rows), it appears as a grouped row. Expand it to inspect each concrete run with its run config, browser, viewport, status, and duration. Click any concrete run row to view detailed results including screenshots, video, and step-by-step trace.

​

Analytics Tab

The Analytics tab provides deeper insights into the run’s results. Analytics are organized in a two-column layout: Left Column:

• New Failures & Flaky Tests - Tests that failed in this run but passed in previous runs. Each test shows how many times it previously passed, with a “Flaky” badge for inconsistent tests.
• Failure Categories - A donut chart showing the distribution of failure types (e.g., Locator Error, AI Failure, Assertion Failed, Timeout). Helps you identify systemic issues at a glance.

Right Column:

• Failing Steps - A scrollable list of every failing step across all test cases. Each entry shows the step action, the error message, the failure category, and how many times that step failed. This is where you go to understand what exactly is breaking.

When all tests pass, the analytics tab shows a success message instead. While tests are still running, analytics are not available until execution completes.

​

Related