Running tests on branches

By running tests on branches, you can check changes and merge once you're certain that both the tests and app under test don't have any issues. You can run both individual tests and plans on a branch.

Running a single test on a branch

In the mabl Trainer

Open the test in the Trainer and take the following steps:

1. Make sure the appropriate branch has been selected in the branch dropdown at the top of the Trainer window.
2. Move the cursor to the top of the Trainer window.
3. Click the play button.

Ad hoc

Navigate to the Test Details page for the test you'd like to run, and take the following steps:

1. Select the desired branch from the branch dropdown at the top of the page.
2. Click on the "Run test" button.
3. Select "Local run" or "Cloud run." Make any other configurations as needed. If you're testing a preview environment, or any testing environment, with an arbitrary and changing URL, you can use the URL override option to specify the URL you want to use.
4. Click the "Start run" button at the bottom. Cloud runs will appear with a branching icon indicating that this run is not on the master branch.

Running test plans on branches

To run a plan on a branch, navigate to the Plan Details page and take the following steps:

1. Click the menu dropdown next to the "Run plan" button.
2. Select "Run on branch." A "Configure plan run" menu will appear.
3. Choose the branch you'd like to run the plan on. You can override the testing environment URL if needed.
4. Click "Run now." If a plan is run on a branch, you will see it marked with a branch icon. If you hover over the icon, the name of the branch that the plan was triggered against will appear.

📘

Branches and plans

Plans are not branched but they are branch aware. Practically speaking, this has the following implications:

• If a plan runs on a branch, the plan will use the latest version of each test on that branch. If one or more tests don't exist on the branch, the plan will use the latest version on master for those tests. If a test exists neither on master nor on the branch in which the plan is running, it will be skipped.
• If a plan runs on master and one or more tests in the plan don't have a version on the master branch, the plan will skip those tests.