Difference between revisions of "PARALLELIZE TESTS"

From Test Automation Patterns
Jump to navigation Jump to search
m (Topic titles in capital letters)
 
(One intermediate revision by the same user not shown)
Line 15: Line 15:
 
''<span style="font-size: 16px">[[INEFFICIENT EXECUTION]]</span>''
 
''<span style="font-size: 16px">[[INEFFICIENT EXECUTION]]</span>''
 
=<span style="font-size: 16px">'''Experiences'''</span>=
 
=<span style="font-size: 16px">'''Experiences'''</span>=
<span style="font-size: 16px">If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 14px">.</span></div>
+
 
 +
<span style="font-size: 16px">If you have also used this pattern and would like to contribute your experience to the wiki, please go to [[Feedback]] to submit your experience or comment.</span><br /> <br />  
 +
 
 +
 
 +
<span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span><br /> <span style="font-size: 14px">.</span></div>

Latest revision as of 16:04, 21 August 2018

.................................................................................................................Main Page / Back to Execution Patterns/ Back to Test Automation Patterns

Pattern summary

In order to save time, run tests in parallel

Category

Execution

Context

Use this pattern when you have a great number of test to execute in a short time

Description

Instead of running all your tests sequentially, you break them up in different batches that can run concurrently on different machines

Implementation

The first step is to write the tests as INDEPENDENT TEST CASES. Another good way to do this is to GET ON THE CLOUD

Potential problems

Be careful not to run the same tests in parallel!

Issues addressed by this pattern

INEFFICIENT EXECUTION

Experiences

If you have also used this pattern and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.


.................................................................................................................Main Page / Back to Execution Patterns/ Back to Test Automation Patterns
.