Difference between revisions of "PARALLELIZE TESTS"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
m (Topic titles in capital letters) |
||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Execution Patterns]]/ Back to [[Test Automation Patterns]]</span> | ||
| − | =<span style="font-size: 16px">Pattern summary</span>= | + | =<span style="font-size: 16px">'''Pattern summary'''</span>= |
<span style="font-size: 16px">In order to save time, run tests in parallel</span> | <span style="font-size: 16px">In order to save time, run tests in parallel</span> | ||
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Execution</span> | <span style="font-size: 16px">Execution</span> | ||
| − | =<span style="font-size: 16px">Context</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
<span style="font-size: 16px">Use this pattern when you have a great number of test to execute in a short time</span> | <span style="font-size: 16px">Use this pattern when you have a great number of test to execute in a short time</span> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Description'''</span>= |
<span style="font-size: 16px">Instead of running all your tests sequentially, you break them up in different batches that can run concurrently on different machines</span> | <span style="font-size: 16px">Instead of running all your tests sequentially, you break them up in different batches that can run concurrently on different machines</span> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">The first step is to write the tests as [[INDEPENDENT TEST CASES]]. Another good way to do this is to [[GET ON THE CLOUD]] </span> | <span style="font-size: 16px">The first step is to write the tests as [[INDEPENDENT TEST CASES]]. Another good way to do this is to [[GET ON THE CLOUD]] </span> | ||
| − | =<span style="font-size: 16px">Potential problems</span>= | + | =<span style="font-size: 16px">'''Potential problems'''</span>= |
<span style="font-size: 16px">Be careful not to run the same tests in parallel!</span> | <span style="font-size: 16px">Be careful not to run the same tests in parallel!</span> | ||
| − | =<span style="font-size: 16px">Issues addressed by this pattern</span> | + | =<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>= |
''<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 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> | ||
Revision as of 18:41, 29 April 2018
.................................................................................................................Main Page / Back to Execution Patterns/ Back to Test Automation Patterns
.................................................................................................................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
Experiences
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!.................................................................................................................Main Page / Back to Execution Patterns/ Back to Test Automation Patterns
.