Each plan has a Plan Details page, where you can review a plan's setup and run history. To find the Plan Details page in the app, click on Plans in the left-hand navigation menu and select the name of the plan that you would like to review.
At the top left corner of the Plan Details page there is a row of icons that can help you complete the following actions:
- Edit the plan
- Enable or disable email notifications for plan runs.
- Create a duplicate of the plan.
- Delete the plan.
- View mabl CLI IDs.
Below the top navigation actions, you can find the settings for the plan, including:
- The name and description of the plan
- The last person to update it (and when)
- The tests in the plan
- The target application and environment
- The plan trigger(s)
- The browser(s)
You can trigger a plan run manually by clicking on the Run plan button. If you want to run the plan on a branch, follow the instructions outlined here.
The toggle next to the Run plan button manages the state of the plan: active or inactive plan.
- A plan should be active if you want to run it on a schedule or use a deployment trigger.
- A plan should be inactive if you don't want it to run on a schedule or get triggered by deployment events. If a plan is inactive, you can still trigger a run by clicking on the Run plan button.
The History section of the Plan Details page includes two charts:
- Plan run history, organized by status and date
- Plan duration trends
You can export plan run results into a CSV file by clicking on the Download CSV button.
In order to keep the results manageable, CSV output is limited to 200 rows. If you require more data, you may be interested in our BigQuery Feed Export Feature
The results for each plan run are listed on the bottom half of the page. They can be filtered by run status:
Clicking on a specific plan run displays test run details.
Plan run time
When a plan run is triggered, it sends a message to the cloud to start running the tests, and then the individual tests start running. The plan run time measures the time it takes from when that message gets sent to the moment all tests are completed. In some cases, tests don't start running immediately, and for this reason you may notice a difference between the total run time of tests in a plan and the run time of a plan.
Updated 18 days ago