Difference between revisions of "AUTOMATE EARLY"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| (8 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 [[Management 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 [[Management 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">Start to automate as early as possible. The sooner automated tests can be run the sooner you can see results</span> | <span style="font-size: 16px">Start to automate as early as possible. The sooner automated tests can be run the sooner you can see results</span> | ||
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Management</span> | <span style="font-size: 16px">Management</span> | ||
| − | =<span style="font-size: 16px">Description</span>= | + | =<span style="font-size: 16px">'''Context'''</span>= |
| + | <span style="font-size: 16px">This pattern is needed if you want to have results as soon as possible</span> | ||
| + | =<span style="font-size: 16px">'''Description'''</span>= | ||
<span style="font-size: 16px">Start to automate as early as possible. The sooner you can run automated tests the sooner you can get results: </span><br /> | <span style="font-size: 16px">Start to automate as early as possible. The sooner you can run automated tests the sooner you can get results: </span><br /> | ||
| − | |||
* <span style="font-size: 16px">if you work side by side with the developers from the very beginning, you will be able to see to it that the Software Under Test (SUT) is developed as [[TESTABLE SOFTWARE]] </span> | * <span style="font-size: 16px">if you work side by side with the developers from the very beginning, you will be able to see to it that the Software Under Test (SUT) is developed as [[TESTABLE SOFTWARE]] </span> | ||
* <span style="font-size: 16px">the developers have feedback from the beginning</span> | * <span style="font-size: 16px">the developers have feedback from the beginning</span> | ||
* <span style="font-size: 16px">Management will be more ready to support you if you show quickly a return on investment</span> | * <span style="font-size: 16px">Management will be more ready to support you if you show quickly a return on investment</span> | ||
| + | =<span style="font-size: 16px">'''Implementation'''</span>= | ||
| + | <span style="font-size: 16px">Start to automate a [[STEEL THREAD]] or [[AUTOMATE WHAT'S NEEDED]]. If you support [[DATA-DRIVEN TESTING]] or [[KEYWORD-DRIVEN TESTING]] testers will be able to write automated test cases even before the SUT is fully implemented.</span><br /> | ||
| + | =<span style="font-size: 16px">'''Potential problems'''</span>= | ||
| + | <span style="font-size: 16px"> <span style="font-size: 16px">Beware of ''[[TOO EARLY AUTOMATION]]'': you would invest a lot of effort to produce only “noise”!</span> | ||
| + | =<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>= | ||
| + | ''<span style="font-size: 16px">[[HIGH ROI EXPECTATIONS]]</span>'' | ||
| + | =<span style="font-size: 16px">'''Experiences'''</span>= | ||
| + | |||
| + | <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 /> <br /> | ||
| − | + | <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 14:45, 21 August 2018
.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns
Pattern summary
Start to automate as early as possible. The sooner automated tests can be run the sooner you can see results
Category
Management
Context
This pattern is needed if you want to have results as soon as possible
Description
Start to automate as early as possible. The sooner you can run automated tests the sooner you can get results:
- if you work side by side with the developers from the very beginning, you will be able to see to it that the Software Under Test (SUT) is developed as TESTABLE SOFTWARE
- the developers have feedback from the beginning
- Management will be more ready to support you if you show quickly a return on investment
Implementation
Start to automate a STEEL THREAD or AUTOMATE WHAT'S NEEDED. If you support DATA-DRIVEN TESTING or KEYWORD-DRIVEN TESTING testers will be able to write automated test cases even before the SUT is fully implemented.
Potential problems
Beware of TOO EARLY AUTOMATION: you would invest a lot of effort to produce only “noise”!
Issues addressed by this pattern
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.
.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns