Maximum concurrency in execution stages

With the latest release, mabl now supports concurrency limits on parallel test plan stages. Previously stages could only be run entirely in sequence or entirely in parallel, requiring tests to be split into more stages if tighter control over concurrency was needed.

Setting a concurrency limit is recommended for all plan stages moving forward and provides a number of benefits:

• Most applications, particularly in pre-production environments, have limited underlying resources. A reasonable concurrency limit allows you to take advantage of speeding up your tests by running in parallel without risking overloading the underlying servers
• Leveraging concurrency limits allows you to avoid adding excess plan stages just to limit test tests in parallel or enable stopping once you get a failure
• When tests fail or are flaky in a parallel plan but pass individually, you can reduce the concurrency limit before resorting to running fully in sequence

To configure a concurrency limit, go to the plan edit screen and click the write icon on any stage. The concurrency limit also works with the switch to always run all tests in a stage, even if there are already failures.

As part of this change, new plan stages will default to a max concurrency limit of 50 tests. Previously defined parallel plan stages will continue to run up to 1000 tests in parallel.

🚧

Note: This represents the number of tests scheduled to run in parallel but is not a guarantee of a specific load on the underlying application as test runs could be starting, completing, or actively running.

You can learn more about plan stage settings here.