Difference between revisions of "TEMPLATE TEST"
m (Topic titles in capital letters) |
|||
| Line 3: | Line 3: | ||
<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><br /> |
| − | <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>= | ||
| Line 10: | Line 10: | ||
=<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">'''Potential Problems'''</span>= | ||
| + | <span style="font-size: 16px">The template needs to be accepted and used by everyone if it is to act as a standard. Having everyone contribute to the design of the template can help to overcome some resistance to using it. </span> | ||
| + | |||
| + | =<span style="font-size: 16px">'''Issues addressed by this pattern'''</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 14:58, 26 June 2018
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.
Potential Problems
The template needs to be accepted and used by everyone if it is to act as a standard. Having everyone contribute to the design of the template can help to overcome some resistance to using it.
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 Design Patterns / Back to Test Automation Patterns