Difference between revisions of "TEMPLATE TEST"

From Test Automation Patterns
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 [[Design 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 [[Design 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">Define a template test case as a standard from which you can drive all kinds of test case variations.</span>
 
<span style="font-size: 16px">Define a template test case as a standard from which you can drive all kinds of test case variations.</span>
=<span style="font-size: 16px">Category</span>=
+
=<span style="font-size: 16px">'''Category'''</span>=
 
<span style="font-size: 16px">Design</span>
 
<span style="font-size: 16px">Design</span>
<span style="font-size: 16px">Context</span>
+
<span style="font-size: 16px">'''Context'''</span>
 
<span style="font-size: 16px">Use this pattern to develop test automation eficiently. For disposable scripts is is not necessary but still quite useful</span>
 
<span style="font-size: 16px">Use this pattern to develop test automation eficiently. For disposable scripts is is not necessary but still quite useful</span>
=<span style="font-size: 16px">Description</span>=
+
=<span style="font-size: 16px">'''Description'''</span>=
 
<span style="font-size: 16px">Define a standard automated test case. New test cases can be created by varying only one data field at a time. This makes it much easier to write new tests. In fact the process of varying the data may also be able to be automated (although remember that you also need to know what the expected result of the test will be).</span>
 
<span style="font-size: 16px">Define a standard automated test case. New test cases can be created by varying only one data field at a time. This makes it much easier to write new tests. In fact the process of varying the data may also be able to be automated (although remember that you also need to know what the expected result of the test will be).</span>
=<span style="font-size: 16px">Implementation</span>=
+
=<span style="font-size: 16px">'''Implementation'''</span>=
 
<span style="font-size: 16px">The standard test case should drive the Software Under Test (SUT) in what should be the most common usage, for instance you set up a standard user with the most common characteristics. To create new tests you can then, based on this benchmark, vary the details to check the possible combinations of values.</span>
 
<span style="font-size: 16px">The standard test case should drive the Software Under Test (SUT) in what should be the most common usage, for instance you set up a standard user with the most common characteristics. To create new tests you can then, based on this benchmark, vary the details to check the possible combinations of values.</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 [[Design Patterns]] / Back to [[Test Automation Patterns]]</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 [[Design Patterns]] / Back to [[Test Automation Patterns]]</span></div>

Revision as of 09:00, 30 April 2018

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

Pattern summary

Define a template test case as a standard from which you can drive all kinds of test case variations.

Category

Design Context Use this pattern to develop test automation eficiently. For disposable scripts is is not necessary but still quite useful

Description

Define a standard automated test case. New test cases can be created by varying only one data field at a time. This makes it much easier to write new tests. In fact the process of varying the data may also be able to be automated (although remember that you also need to know what the expected result of the test will be).

Implementation

The standard test case should drive the Software Under Test (SUT) in what should be the most common usage, for instance you set up a standard user with the most common characteristics. To create new tests you can then, based on this benchmark, vary the details to check the possible combinations of values.

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 Design Patterns / Back to Test Automation Patterns