Test Plans
Schedule and organize test suite executions
Test Plans
Test Plans allow you to schedule and organize the execution of multiple test suites and individual test cases. They provide a powerful way to automate your testing workflow by running collections of tests on a recurring schedule.
What are Test Plans?
A Test Plan is a container that groups together:
- Test Suites - Collections of related test cases
- Test Cases - Individual tests
- Scheduling Configuration - When and how often to run the tests
- Environment Settings - Which environment to run tests against
- Notification Settings - Who to notify about test results
Creating a Test Plan
Basic Information
- Test Plan Name - A descriptive name for your test plan
- Environment - Select which environment the tests should run against, or choose “No Environment” to use default settings
Adding Tests
You can add tests to your plan in two ways:
Test Suites
Add entire test suites to run all test cases within them. This is useful for:
- Running comprehensive feature tests
- Executing regression test suites
- Testing complete user workflows
Individual Test Cases
Add specific test cases for more granular control. This is helpful for:
- Running critical path tests
- Focusing on specific functionality
- Creating custom test combinations
Email Notifications
Configure up to 10 email addresses to receive notifications about test plan results:
- Enter email addresses in the notification field
- Press comma or Enter to add each email
- Remove emails by clicking the X next to them
Recipients will be notified when:
- Test plan execution starts
- Test plan execution completes
- Test failures occur
Scheduling
Test plans support flexible scheduling using a visual date and time picker:
Schedule Options
- One-time execution - Run the test plan once at a specific date and time
- Recurring execution - Set up regular intervals (daily, weekly, monthly, yearly)
- Custom recurrence - Define complex scheduling patterns
Schedule Examples
- Daily at 9 AM - Run every morning before the team arrives
- Weekly on Fridays - End-of-week regression testing
- Monthly on the 1st - Monthly comprehensive testing
- Custom patterns - Every weekday, specific days of the month, etc.
Managing Test Plans
Viewing Test Plan Details
The test plan details page shows:
Overview Metrics
- Total - Number of test cases in the plan
- Passed - Number of successful test executions
- Failed - Number of failed test executions
- Last Run - When the plan was last executed
Schedule Information
- Current schedule configuration in human-readable format
- Environment the plan is configured to run against
Tabs
- Test Suites - View and manage included test suites
- Test Cases - View and manage individual test cases
- Runs - View execution history and results
Running Test Plans
Manual Execution
Click the Run All button to execute the test plan immediately against your currently selected environment.
Note: The Run button is disabled if the test plan contains no test suites or test cases.
Scheduled Execution
Test plans automatically execute according to their configured schedule using the specified environment.
Editing Test Plans
- Click Edit on the test plan details page
- Modify any configuration (name, schedule, environment, notifications)
- Click Save to apply changes
Adding/Removing Tests
Adding Tests
- Click Add Tests on the test plan details page
- Select additional test suites or test cases
- Click Save to add them to the plan
Removing Tests
- Navigate to the Test Suites or Test Cases tab
- Click the trash icon next to any test you want to remove
- The test is immediately removed from the plan
Viewing Test Results
Execution History
The Runs tab provides:
History Chart
- Visual representation of test execution results over time
- Filter results by date range
- Track trends in test success/failure rates
Recent Runs Table
- Detailed list of recent test plan executions
- Execution status, duration, and timestamps
- Links to detailed test results
Individual Test Results
Click on any test suite or test case to view:
- Detailed execution logs
- Step-by-step results
- Screenshots and error information
- Performance metrics
Best Practices
Organizing Test Plans
- Feature-based plans - Group tests by application features
- Environment-specific plans - Separate plans for staging, production testing
- Priority-based plans - Critical tests vs. comprehensive regression suites
Scheduling Strategy
- Peak hours avoidance - Schedule during low-traffic periods
- Notification timing - Consider recipient time zones
- Frequency balance - More frequent for critical paths, less for comprehensive suites
Notification Management
- Relevant recipients - Only notify stakeholders who need the information
- Clear naming - Use descriptive test plan names for easy identification
- Escalation paths - Include both developers and QA team members
Troubleshooting
Common Issues
Test Plan Won’t Run
- Ensure at least one test suite or test case is added
- Verify the selected environment is accessible
- Check that tests are not currently running
Schedule Not Working
- Verify schedule configuration is correct
- Check system time and timezone settings
- Ensure sufficient execution slots are available
Missing Notifications
- Verify email addresses are correctly formatted
- Check spam/junk folders
- Ensure notification settings are enabled
Getting Help
If you encounter issues with test plans:
- Check the execution logs in the Runs tab
- Verify your environment and test configurations
- Contact support with specific error messages and test plan details