Running Automated Tests in Parallel (Part 1)

Posted Nov 26th, 2012

This post was originally written by Alan Parkinson of Hindsight Software. One of Sauce's authorized partners, Hindsight Software specializes in building tools and services around Selenium and test automation. It has been reprinted with his permission. Automated functional tests provide valuable feedback to developers by notifying them when they have completed or broken functionality. The value of these tests can be maximised by providing the test results in the shortest possible time. The reason being the problem is likely to be fresh in the developer's mind and quicker for them to fix. A typical functional or UI test suite can take many hours to run because the tests can only be run sequentially. The main cause for the sequential tests is the dependence on data. Common practice has test cases clear the database of the application under test and populate it with the required data before it starts. This high level of database manipulation does not allow the tests to be run in parallel because each test will interfere with the database at different times, therefore corrupting data required used by other tests. To continue reading this post, jump over to the Hindsight blog

Written by

The Sauce Labs Team


Automated TestingSelenium