Test plans

A plan is a reusable set of test cases, each ticked on the browser profiles it should run on, against one environment.

Note

Plans have no status, owner field or due date. You can run a plan whenever you like and change it between runs.

Create a plan

Click Test plans in the sidebar, then New plan.

In "Create plan", choose the Project, enter a Name and an optional Description, and pick the Environment the plan runs against.

Click Create plan, then add test cases on the plan's page.

If no environment is offered, add one in the project's Materials → Configuration first.

The browser matrix

A plan's page is a matrix: one row per test case, one column per browser profile. A ticked cell means "run this case on this browser".

Click Add cases, filter or Select all, then click Add. New rows start on Chrome.
Click a cell to tick it, or drag across cells to tick or untick a whole region. Click a column header to toggle the whole column.
Each row's Targets preset applies a ready-made set: "Chrome only", Full desktop, Mobile smoke or Everything. Apply to all rows copies it to every row.
A row's menu has Open the test case and Remove from plan.
A disabled browser profile can be unticked but not added.
A test case can belong to many plans.

The Release 2.4 regression plan: ten test cases as rows and six browser profiles as columns, Chrome ticked on every row and Firefox on one, a dataset bound to the login case, and the launch bar with 12 executions — A plan's browser matrix. The login row is bound to a two-row dataset, so the plan runs 12 executions.

Datasets per row

Each row has a Dataset: None — runs once, or a dataset, in which case the row runs once per dataset row on each ticked browser. The number of executions is ticked cells × dataset rows.

Only Active cases run

Rows whose case is not Active show "Not Active — skipped when the plan runs". If no case in the plan is Active, all of them run.

Warning

New cases start as Draft and Qalion AI cases as In review. Set them to Active, or they will be skipped as soon as the plan holds one Active case.

Run a plan

The launch bar at the bottom of the plan shows what a run will do:

The number of executions, and how many batches they run in.
How many browser sessions your organization has free right now.
Parallel: how many executions run at the same time, up to 4 per run and within your organization's limit.
Tunnel: appears when a tunnel connector is running. Pick it to test a private app (see Private apps).

Click Run followed by the number of executions. Qalion opens the run. From the plans list, a row's Run action opens a dialog with a Parallel sessions slider and Run now, and you stay on the list.

Note

A run is refused when your organization has no credits left ("Your organization has no remaining credits.") or has reached its concurrent test limit.

Schedules

Click Schedule on a plan to run it automatically.

Setting	Options
Repeat	Every hour, Every day, Weekdays (Mon–Fri), On chosen days, or Custom (cron). The minimum interval is 15 minutes.
Time	When it runs
Time zone	Any time zone, such as Europe/Paris
Environment	The environment the scheduled runs use
Profiles	A subset of the plan's browser profiles

Turn off Run on this schedule to pause it and keep its settings. Save schedule, Remove and Run now are next to it.
Scheduled runs start as you and use credits like any run. You are notified when a scheduled run is skipped or fails.
Owners, Admins and Testers can edit schedules.

Edit, duplicate, delete

Edit changes the plan's name, description and environment.
Duplicate creates "… (copy)" with the same cases and browsers, without the schedule.
Delete moves the plan to the Trash for 30 days. Its runs stay readable meanwhile and are deleted when the plan is purged.
The plans list can be searched and filtered by Environment, Last run, Schedule (Scheduled, Paused, Not scheduled) and Owner.

Was this page helpful?

Shared steps & datasets

Test runs