This post was originally written by Alan Parkinson ofHindsight Software. One of Sauce & # x27; s authorised partner, Hindsight Software specializes in building tools and service around Selenium and test automation. It has been reprint with his permission.Automated functional tryout provide valuable feedback to developers by notifying them when they receive discharge or broken functionality. The value of these tests can be maximize by supply the test results in the little possible time. The ground being the problem is likely to be fresh in the developer & # x27; s psyche and quicker for them to fix. A typical functional or UI test entourage can take many hours to run because the tests can only be run sequentially. The main cause for the successive trial is the dependence on datum. Common practice has test cases brighten the database of the application under test and dwell it with the required data before it starts. This high degree of database manipulation does not countenance the tests to be run in latitude because each test will intervene with the database at different times, therefore corrupting data required used by other tests.

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

The common resolution for long running tryout suites is to interrupt them into batches and run each batch on a freestanding machine with its own instance of the application under test and its database. This is easy to reach apply supernumerary ironware, Virtual Machine & # x27; s or Cloud computing resources. You don & # x27; t even feature to write code for spinning up new machines, or accession outside machine, as Continuous Integration (CI) servers like Jenkins and Bamboo ply functionality for running figure on multiple estimator. This feature is good known as Slaves or Agents. The majority of the democratic testing instrument have ways of grouping tryout together and we can use this characteristic to make our & quot; Batches & quot; of tests. These characteristic are cognise as & quot; categories & quot; in JUnit, & quot; group & quot; in TestNG and & quot; tags & quot; in Cucumber, Lettuce and Behat.To continue read this post, jump over to the Hindsight blog