Test Runs

A test run is how you execute a set of test cases and track their results — pass, fail, blocked, and more — for a build, a sprint, or a release, and see live progress as the team works through it.

Creating a run

Open the Runs tab of a project and click New run. Give it a name and choose which cases go into it, using one of three modes:

• All cases in project — every case in the project.
• By folders — every case inside the folders you select.
• Pick manually — choose individual cases from a two-panel picker (the same folder-tree-plus-list layout used on the Cases page), with search by name, case number, or full reference (for example KEY-12).

You can also optionally assign the run to a team member, link it to a milestone, and select one or more configurations (see below). A run can be created empty — the dialog warns you but doesn't block it.

Each run gets a project-scoped number (#1, #2, …) instead of an unreadable ID, so /runs/1 is a stable, shareable link. Numbers are never reused, even after a run is deleted.

Running through cases and submitting results

Every case in a run appears as a row with its current status. Click a row to open the case: you'll see its live content (title, priority, tags, preconditions, steps), a result form, and the history of previous results for that row.

To record a result, pick a status, optionally add a comment, and submit. Available result statuses are:

A timer starts automatically when you open a case and records the time spent; the value is informational and factored into the case's history. Submitting your first result in a run automatically moves the run's own status from open to in_progress — you don't need to do this by hand. Closing and reopening a run is a manual action from the run's menu.

The run's progress bar and pass rate are calculated live from the current status of every row, so they're always up to date as results come in.

Assignees

You can assign a run as a whole to a team member (the person responsible for driving it), and separately assign individual cases within the run to whoever is executing them. Assignees must be members of the project. A toggle on the runs list ("Assigned to me") and on a run's case list ("My cases") lets each person jump straight to their own work.

Configurations

If you need to run the same cases against more than one environment — different browsers, operating systems, or a staging vs. production setup — set up named configurations for the project (for example "Chrome / Windows", "Safari / iOS"). When creating a run, select one or more configurations and every case is duplicated into a separate row per configuration, so you can track pass/fail independently for each one.

A run created without any configuration behaves exactly as before — one row per case.

Comparing runs

Open Compare runs from the runs list to see what changed between two runs of the same project — useful for comparing two builds, or a pre-release run against the current one. Select a base run and a compared run; the report is fully shareable by URL, so a teammate opening the same link sees the same comparison.

The report groups cases into:

• Fixed — was failing/blocked, now passes.
• Regressed — was passing, now fails/blocked.
• Still failing — failing or blocked in both runs.
• Added — present only in the compared run.
• Removed — present only in the base run.

Cases that didn't change aren't shown. If a run uses configurations, each case/configuration combination is compared independently.

Sharing a run report

If you need to share a run's results with someone who doesn't have a Proba.run account — a client, a stakeholder, a manager — click Share in the run's header (available to anyone who can manage runs) to generate a public read-only link. Anyone with the link can view a summary report — case titles, statuses, and overall progress — without logging in. Sensitive details (assignees, comments, tags, attachments, custom fields) are never included in the public report.

You choose how long the link stays valid (7, 30, 90 days, or indefinitely), can copy it any time, and can revoke it or generate a new one whenever you want to cut off access.