Overview

Test Execution is where you create and run Test Run Packs — named, reusable groups of tests that you can run on demand or on a schedule.

Everything about a pack's lifecycle happens here: create it, run it now, enable it for scheduled runs, watch its status, and open its run history and reports.

A pack has one of two run types:

Run type	What it contains
Functional	Endpoint tests executed against your API. The default type.
Workflow	A multi-step workflow executed end to end. See Understanding workflows.

Before you begin

You need a project with endpoints and tests already in place. See Endpoint management and Test case.
Nav path: select Execution in the top navigation. The page header reads Test Execution, with New Test Run Pack at the top-right.

Create a new pack

Select New Test Run Pack. This opens the pack wizard, where you name the pack, choose its tests, and set execution preferences step by step.

The wizard is documented in full at Test run pack wizard.

The Test Run Packs table

Existing packs are listed under Test Run Packs. The table has these columns:

Column	What it shows
Enabled	Whether the pack is active for scheduled runs. Toggle it here.
Pack ID	The pack's unique id. Use Copy Pack ID to copy it.
Name	The pack name you set in the wizard.
Description	The pack description.
Project	The project the pack belongs to.
Run Type	Functional or Workflow.
Test Count	How many tests the pack contains.
Last Updated By	The user who last changed the pack. Shows Unknown if unattributed.
Last Updated	When the pack was last changed.
Status	The outcome of the most recent run.
Upcoming Schedule	The next scheduled run time, or Never if the pack isn't scheduled.
Actions	Per-pack controls — see below.

If no packs exist yet, the table shows No test run packs found.

Run a pack

In the Actions column:

Select Run Now to start the pack immediately.
While a run is in progress, the control becomes Cancel Run — use it to stop the run.

Run outcomes use four canonical statuses:

Status	Meaning
Passed	The test succeeded.
Failed	An assertion or validation failed.
Error	Execution or transport failed — the test could not complete.
Not run	The test was skipped.

The distinction between Failed and Error matters when triaging: Failed means your API responded and the response didn't match expectations; Error means the request itself couldn't be completed.

Enable, disable, and scheduling

The Enabled toggle controls whether a pack participates in scheduled runs. Turning it on recalculates the pack's Upcoming Schedule; turning it off clears it to Never.

Toggling Enabled does not affect Run Now — you can always run a pack manually regardless of its enabled state.

Scheduling itself is configured in the wizard's execution preferences step. See Test run pack wizard.

View runs and reports

Select View Runs on a pack to open its run history. If the pack has never run, the list shows No runs found.

From a run, select View details to open the results. Depending on what you need:

High level test report — pass/fail summary across the pack.
Detailed test report — per-test request, response, and assertion detail.

Edit or delete a pack

Edit reopens the pack in the wizard so you can change its name, tests, or execution preferences.
Delete Test Run Pack removes the pack. You'll be asked to confirm first.

Deleting a pack does not delete the underlying tests or endpoints — only the pack that groups them.

Find a pack

For large pack lists:

Search packs… filters the table as you type.
Select any sortable column header to sort by it; select again to reverse.
Use the column visibility menu to show or hide columns.
Reset filters clears the search and filters in one step.
Pagination shows 25 packs per page by default, with First / Previous / Next / Last page controls.

Troubleshooting

"Failed to toggle pack enabled status" — the enable/disable request didn't reach the server. Check your connection and retry; if it persists, see Debug logging.
Upcoming Schedule shows "Never" on a pack you scheduled — confirm the Enabled toggle is on. A disabled pack has no next run time.
Status is Error rather than Failed — the request couldn't complete at all (host unreachable, TLS, timeout). Check the endpoint and environment before looking at assertions.
Test Count is lower than expected — the pack's test selection was saved with fewer tests than you intended. Reopen it with Edit and recheck the selection step.

Best practices

Keep packs scoped to a purpose — a smoke pack, a regression pack — rather than one pack containing everything. Smaller packs are faster to triage.
Disable rather than delete packs you're not currently running. You keep the history and can re-enable later.
Use Copy Pack ID when referencing a pack from CI or the public API. See Public API.
Triage Error before Failed after a run — transport problems often cascade and produce failures that aren't real.

Test Execution: Run and Manage Test Run Packs