Product documentationUpdated March 18, 2026
Manage and Run Execution Packs
After creating a pack, run it now, edit configuration, monitor status, and manage lifecycle actions from the Execution list.
Overview
A test run pack is a reusable group of test cases executed together.
After creating a pack with the wizard, manage it from the Execution list.
Common pack actions
For each pack in the list, typical actions include:
- Run Now: execute immediately.
- View Run: open latest or selected run details.
- Edit: update pack details, tests, execution preferences, and schedule.
- Delete: remove obsolete packs.
- Enable/Disable: toggle scheduled execution where supported.
Monitoring execution packs
Use pack list data to monitor:
- current status
- last run time
- next scheduled run
- pass/fail outcomes
- execution trends via linked reports
Typical lifecycle
- Create pack in wizard.
- Run once to validate auth and environment.
- Enable recurring schedule if required.
- Monitor outcomes and tune flaky tests.
- Update pack scope as APIs evolve.
Best practices
- Keep separate packs for smoke, regression, and release checks.
- Validate pack configuration with a manual run before scheduling.
- Keep notifications enabled for failed or critical runs.
- Review reports regularly and remove unstable tests from gated packs.
Related articles
Related articles
- Open Execution and Start a New Pack · Product documentation
- Create an Execution Pack (Wizard) · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.