What Test Plans Do
- Bundle multiple test suites into one run
- Reuse saved suite configuration so you don’t have to reconfigure tests every time
- Orchestrate runs across environments (dev, staging, production) and viewports (mobile, desktop)
- Execute suites in parallel where possible to reduce total runtime
How Configuration Works
Each suite inside a Test Plan keeps its own saved configuration. For every suite you add, you can adjust:- Environments – Choose which environments the suite will run on (for example, dev, staging, production)
- Viewports – Select Mobile, Desktop, or both for each suite
- Scenarios – Pick specific scenarios from scenario tables to cover different data or user flows
- Individual tests – Exclude individual tests from a suite when they are not needed for this plan
- Browsers – Define the default browsers for the plan (Chrome, Safari, Microsoft Edge, Firefox) to control cross‑browser coverage
How Executions Run
When you run a Test Plan:- All included suites start from a single action (Run Plan or a scheduled trigger)
- Spur runs suites in parallel wherever possible to speed up feedback
- You still get granular results per suite and per test, including pass/fail status and timings
- Each execution appears in your run history with links back to suite runs for debugging
Learn More
Detailed guide for creating Test Plans
Key Benefits
Comprehensive Coverage
Test entire applications with one execution, not individual tests or suites.
Organized Testing
Group related tests for releases, sprints, or feature deployments.
Consistent Results
Maintain identical test configurations and scenarios across all executions.
Parallel Execution
Run tests across environments and browsers simultaneously.
When to Use Test Plans
Release Validation
Validate critical functionality before production deployment.- All critical path tests
- Staging + Production environments
- All supported browsers
- Run before deploy
Nightly Regression
Execute comprehensive overnight testing across your entire application.- All test suites
- Dev + Staging environments
- Primary browsers
- Schedule: Daily at 2 AM
Cross-Browser Testing
Ensure compatibility across different browser environments.- Core features
- Staging environment
- Chrome, Safari, Firefox, Mobile
- Schedule: Weekly
Production Monitoring
Continuously validate critical user journeys in production.- Critical user journeys
- Production environment only
- Chrome desktop
- Schedule: Every 30 minutes