In mabl, a plan contains one or more tests that run in parallel or sequential order. Additionally, a plan contains all of the information that tests need to run, including application and environment settings, device settings, and specific triggers to run on a schedule or by deployment.
After you create some tests for your application, you can add them to a plan. This article explains the settings you can configure for a plan.
Not sure which tests should run together in a plan? Check out our article on organizing tests into a plan.
Plan settings for a new plan
The basic information for a plan includes the plan name, description, and labels. Plan name and description appear on the Plans page and the Plan Details page. Plan labels define test suites and can be used to run tests in tandem as a mabl deployment event.
You must associate your plan with an environment and application.
If the application has multiple environments, you may associate the plan with one or more environments. When you run a plan, every test in the plan runs once per environment. For example, if you associate a plan with the "dev" and "staging" environments, the plan runs tests once in the "dev" environment and once again in the "staging environment.
Environment settings for a plan
If the plan includes browser tests, select at least one web URL (`app.url`).
If the application and environment include multiple web URLs (`app.url`), you may configure the plan to run against one or more web URLs. Every browser test runs once per web URL.
Mobile build files
If the plan includes mobile tests, select a mobile build file to run the tests against.
If the plan includes API tests, select an API URL to run tests against. You may only select one API URL per test.
Plans must always contain one or more tests. Click on the Add tests button to add an existing test.
Adding tests to a plan
By default, tests run in parallel in one stage. Depending on your use case, you may organize tests to run in multiple stages or with specific settings for concurrency or failure behavior.
The Add stage button adds a new plan stage. When a plan with stages runs in the cloud, tests in a prior stage complete before tests in the subsequent stage start running.
Adding a new plan stage
Within a plan stage, you may configure additional settings, such as concurrency, behavior on failure, and overrides. See the article on plan stage settings for more details.
Editing stage options
Browser device settings
If the plan contains browser tests, you may configure the following browser device settings at the plan level:
- Desktop (default) or mobile web testing
- Advanced settings - open the Additional settings dropdown
Mobile device settings
If the plan contains mobile tests, you may override the following mobile device settings specified at the test level:
- Mobile device
- OS Version
For more information on running plans on all the different ways to trigger a plan run, click here.
Toggle on Show advanced options to view additional settings: credentials, the run multiplier, and retry settings.
If the plan includes tests with logins, you may associate the plan with existing mabl credentials or create a new set of mabl credentials.
Use run multiplier settings to spin up multiple instances of each test in the plan.
Set plans triggered by a schedule or a deployment event to automatically re-run all tests or just the failed tests.
To re-run manually triggered plans, click on the plan re-run button next to the plan run.
Rerunning a plan that was triggered manually