Creating a plan to run tests

Plans, along with tests, make up two of the core features of mabl. A plan runs all of the tests that it contains, which can be as many or as few as you need, in parallel or sequential order. Additionally, a plan contains all of the information that tests need to run, including, but not limited to URLs, browsers, and the specific timing triggers.

📘

Organizing tests into plans

If you're looking for tips on how to organize your tests into a plan, check out this guide.

This guide provides an overview on how to create and configure a plan.

Creating a new plan

To create a plan, select Plans in the left-hand navigation bar and click the New Plan button in the right-hand side of the window.

A New Plan form will appear. At a minimum, you must define the following settings for a plan:

• Plan name
• Environment(s) to run the tests in
• Application under test
• Tests included in the plan

When you're happy with the settings, click Save plan to confirm your settings. For a full overview of the configurations that can be applied to a plan, see the following section on plan settings.

Plan settings

The basics

Enter a name for the plan. We recommend that you define a naming convention with the other members of your workspace so that you can easily locate plans and understand what they do.

Optionally, you can also add a description and label(s).

👍

Plan labels

Plan labels can be used to define specific test suites, such as regression, targeted regression, smoke, or a certain functionality or feature area.

They are helpful for targeting specific plans in mabl deployment events.

Environments

When you click on the + Add environments button, an Environments modal will appear:

• Select the Application from the dropdown.
• Check the environment(s) you wish to run the plan in.
• Click Save.

Plans can be configured to run against only one environment or multiple environments.

Tests

Select the test(s) that you would like to include in the plan. Tests in a plan are grouped according to stages. A plan stages specify the order in which tests will run in a plan.

📘

Turning tests on and off

A plan run will only trigger the tests in the plan that are turned on. If none of the tests are turned on, the Run plan button on the Plan Details page is disabled. For more information on how to turn tests on and off, see this guide.

Device settings

Device settings that can be configured at the plan level include:

• Desktop (default) or mobile testing
• Browser(s)
• Advanced options
  • Page interaction speed
  • HTTP basic auth and custom headers
  • Visual change learning

Triggers

In addition to triggering a plan manually by clicking on the Run plan button, you can configure a plan to run on a schedule, by deployment, or on a timer.

For more information on running plans on a schedule, see Scheduling tests.

📘

Limitation

It is not possible to trigger a local plan run. For more information, see our Plan FAQs.

Advanced

Advanced options for plan configurations include:

• Credentials: Associate the plan with login credentials
• Run multiplier: Spin up multiple instances of each test in the plan.
• Retry settings: If a plan fails, you can configure it to automatically run all tests or just the failed tests one more time.