​

Plans

Test Plans let you schedule and organize the execution of multiple test cases at once. You can include tests by selecting individual test cases and/or entire folders. Plans can be run on demand or on a recurring schedule.

​

What are Test Plans?

A Test Plan is a container that groups together:

• Folders: Include all test cases within selected folders (including nested subfolders)
• Test Cases: Individual tests you select explicitly
• Scheduling Configuration: When and how often to run
• Environment Settings: Which environment to run against
• Notification Settings: Who to notify about results

​

Creating a Test Plan

​

Basic Information

1. Plan Name: A descriptive name for your plan
2. Environment: Select the environment to run against (or choose “No Environment”)

​

Adding Tests

You can add tests to your plan in two ways:

​

Folders

Add one or more folders to include all test cases within them. This is useful for:

• Running all tests for an area or feature
• Keeping plan membership in sync as new tests are added to those folders

​

Individual Test Cases

Add specific test cases for more granular control. This is helpful for:

• Critical‑path or smoke test collections
• Curating a custom, lightweight regression set

​

Email Notifications

Configure up to 10 email addresses to receive notifications about plan results:

1. Enter email addresses in the notification field
2. Press comma or Enter to add each email
3. Remove emails by clicking the X next to them

Recipients are notified when:

• Plan execution starts
• Plan execution completes
• Failures occur

​

Scheduling

Plans support flexible scheduling using a visual date and time picker:

​

Schedule Options

• One‑time execution: Run once at a specific date and time
• Recurring execution: Daily, weekly, monthly, or yearly cadence
• Custom recurrence: Build complex schedules

​

Schedule Examples

• Daily at 9 AM: Morning smoke tests
• Weekly on Fridays: End‑of‑week regression
• Monthly on the 1st: Comprehensive coverage
• Custom patterns: Every weekday, specific month days, etc.

​

Managing Plans

​

Viewing Plan Details

The plan details page shows:

​

Overview Metrics

• Total: Number of test cases included
• Passed: Number of successful executions
• Failed: Number of failed executions
• Last Run: Timestamp of the last execution

​

Schedule Information

• Current schedule (human‑readable)
• Selected environment

​

Tabs

• Tests: View the selected folders and test cases for this plan
• Runs: View execution history and results

​

Running Plans

​

Manual Execution

Click Run All to execute the plan immediately against the selected environment. Note: The Run button is disabled if the plan contains no folders or test cases.

​

Scheduled Execution

Plans automatically run according to their configured schedule using the specified environment.

​

Editing Plans

1. Click Edit on the plan details page
2. Modify any configuration (name, schedule, environment, notifications)
3. Click Save to apply changes

​

Adding/Removing Tests

​

Adding

1. Click Edit Tests on the plan details page
2. Select additional folders and/or test cases
3. Click Save to add them to the plan

​

Removing

1. Open the Tests tab on the plan details page
2. Deselect the folder(s) and/or test case(s) you want to remove
3. Click Save

​

Viewing Results

​

Execution History

The Runs tab provides:

​

History Chart

• Visual trend of execution outcomes over time
• Filter by date range
• Track pass/fail rates

​

Recent Runs Table

• Status, duration, and timestamps
• Links to detailed results

​

Individual Test Results

From any run, click into a test case to see:

• Detailed logs
• Step‑by‑step results
• Screenshots and error context
• Performance metrics

​

Best Practices

​

Organizing Plans

• Feature‑based: Group tests by product area
• Environment‑specific: Separate plans for staging vs production checks
• Priority‑based: Smoke vs full regression

​

Scheduling Strategy

• Avoid peak hours for heavy runs
• Consider recipients’ time zones for notifications
• Balance frequency between critical paths and broad coverage

​

Notification Management

• Add only relevant recipients
• Use clear plan names for easy identification
• Establish escalation paths for failures

​

Troubleshooting

​

Common Issues

Plan Won’t Run

• Ensure at least one folder or test case is selected
• Verify the selected environment
• Check that no conflicting run is active

Schedule Not Running

• Verify schedule configuration and timezone
• Ensure sufficient worker capacity

Missing Notifications

• Verify email formatting
• Check spam/junk folders
• Ensure notifications are enabled

​

Getting Help

1. Check the execution logs in the Runs tab
2. Verify environment and selections in Tests
3. Contact support with run IDs and plan details