Not logged in - Log In / Register

Single machine parallel testing of single branches

Running more than one instance the Launchpad test suite for the one branch at the same time on the same computer. Taking one run of the Launchpad test suite and splitting it up across many different processes on the same computer and gathering the results.

Contact: RobertCollins On Launchpad: https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=paralleltest

As a Technical Architect
I want our automated test runs to parallelise effectively within a single machine
so that the qa and branch promotion pipeline moves faster

As a Developer
I want ec2 runs to parallelise effectively within the ec2 instance
so that landings happen faster


Our test suite execution time is a crucial factor in the minimum cycle type to make a change and deploy it. Similarly our ability to recover from intermittently failing tests is defined by the time it takes the test suite to run.

Having a dramatically faster test suite will reduce the latency for bugfixes, gathering of profile data and repetition/solving of intermittent failures.


All Launchpad developers.

Constraints and Requirements


Nice to have

Must not

Out of scope

Changing the landing technology is out of scope: thats something the SimplifiedMergeMachinery project will evaluate and act on.



How will we know when we are done?

ec2 and buildbot test runs are dramatically shorter than they are today: down to less than 50% of the current time, preferrable 15%-20%

How will we measure how well we have done?


LEP/ParallelTesting (last edited 2012-01-05 22:08:33 by gary)