Difference between revisions of "STEEL THREAD"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| 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">Test a thin slice of functionality that drives the Software Under Test (SUT) from one end to the other.</span> | + | <span style="font-size: 16px">Test a thin slice of functionality that drives the Software Under Test (SUT) from one end to the other (E2E-Tests).</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 begin with test automation or when you start automating new functionality in the SUT that you first have to get to know</span><br /> <span style="font-size: 16px">This pattern is not necessary for writing disposable scripts</span> | <span style="font-size: 16px">Use this pattern when you begin with test automation or when you start automating new functionality in the SUT that you first have to get to know</span><br /> <span style="font-size: 16px">This pattern is not necessary for writing disposable scripts</span> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Description'''</span>= |
<span style="font-size: 16px">A steel thread is a test case that tests a “thin slice of functionality that cuts through the functionality from one end to the other” (Lisa Crispin). This kind of test cases is good to begin with because:</span><br /> | <span style="font-size: 16px">A steel thread is a test case that tests a “thin slice of functionality that cuts through the functionality from one end to the other” (Lisa Crispin). This kind of test cases is good to begin with because:</span><br /> | ||
| − | |||
* <span style="font-size: 16px">You can support testers right away. </span> | * <span style="font-size: 16px">You can support testers right away. </span> | ||
* <span style="font-size: 16px">It will also help you select the [[RIGHT TOOLS]], since you will be able to get a good understanding of where the eventual automation problems are to be found</span> | * <span style="font-size: 16px">It will also help you select the [[RIGHT TOOLS]], since you will be able to get a good understanding of where the eventual automation problems are to be found</span> | ||
| − | =<span style="font-size: 16px">Implementation</span>= | + | =<span style="font-size: 16px">'''Implementation'''</span>= |
<span style="font-size: 16px">Select test cases that perform only minimal actions, but go through the whole application. For instance insert a new customer record with only the mandatory fields.</span> | <span style="font-size: 16px">Select test cases that perform only minimal actions, but go through the whole application. For instance insert a new customer record with only the mandatory fields.</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>''<br /> ''<span style="font-size: 16px">[[LIMITED EXPERIENCE]]</span>'' | ''<span style="font-size: 16px">[[INEFFICIENT EXECUTION]]</span>''<br /> ''<span style="font-size: 16px">[[LIMITED EXPERIENCE]]</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 | + | |
| + | <span style="font-size: 16px">If you have 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></div> | ||
Latest revision as of 10:03, 22 February 2019
.................................................................................................................Main Page / Back to Execution Patterns / Back to Test Automation Patterns
Pattern summary
Test a thin slice of functionality that drives the Software Under Test (SUT) from one end to the other (E2E-Tests).
Category
Execution
Context
Use this pattern when you begin with test automation or when you start automating new functionality in the SUT that you first have to get to know
This pattern is not necessary for writing disposable scripts
Description
A steel thread is a test case that tests a “thin slice of functionality that cuts through the functionality from one end to the other” (Lisa Crispin). This kind of test cases is good to begin with because:
- You can support testers right away.
- It will also help you select the RIGHT TOOLS, since you will be able to get a good understanding of where the eventual automation problems are to be found
Implementation
Select test cases that perform only minimal actions, but go through the whole application. For instance insert a new customer record with only the mandatory fields.
Issues addressed by this pattern
INEFFICIENT EXECUTION
LIMITED EXPERIENCE
Experiences
If you have used this pattern and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.