Difference between revisions of "Failure Patterns"
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Failure patterns show how behaviours that start well can end up as costly failures. These kind of patterns help recognize if an automation project is heading in the wrong direction at a time when countermeasures can still enable a turnaround. Failure patterns are also called "anti-patterns", since they are things that you shouldn't do. In this wiki, they could also be Issues. The table below gives a list of the Failure patterns with a short description.</span><br /><br /><br /> | <div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial; font-size: 16px">Failure patterns show how behaviours that start well can end up as costly failures. These kind of patterns help recognize if an automation project is heading in the wrong direction at a time when countermeasures can still enable a turnaround. Failure patterns are also called "anti-patterns", since they are things that you shouldn't do. In this wiki, they could also be Issues. The table below gives a list of the Failure patterns with a short description.</span><br /><br /><br /> | ||
{| class="wiki_table" border="1" style="border-collapse:collapse" | {| class="wiki_table" border="1" style="border-collapse:collapse" | ||
| − | ! <span style="font-size: 16px">Failure | + | ! <span style="font-size: 16px">Failure Patterns [1]</span><br /> |
! <span style="font-size: 16px">Description</span><br /> | ! <span style="font-size: 16px">Description</span><br /> | ||
|- | |- | ||
| <span style="font-size: 16px">[[ FRAMEWORK COMPETITION]]</span><br /> | | <span style="font-size: 16px">[[ FRAMEWORK COMPETITION]]</span><br /> | ||
| − | + | | <span style="font-size: 16px">Different teams build different automation frameworks and are not able or willing to consolidate them</span><br /> | |
|- | |- | ||
| − | | <span style="font-size: 16px">[[ GOING FOR THE NUMBERS]] | + | | <span style="font-size: 16px">[[ GOING FOR THE NUMBERS]]</span><br /> |
| − | + | | <span style="font-size: 16px">The automation team is pushed into automating as many tests as possible while disregarding test robustness</span><br /> | |
|- | |- | ||
| − | | <span style="font-size: 16px">[[ THE NIGHT TIME FALLACY]] | + | | <span style="font-size: 16px">[[ THE NIGHT TIME FALLACY]]</span><br /> |
| − | + | | <span style="font-size: 16px">Targeting "Night runs" can lead to inefficient automation</span><br /> | |
|- | |- | ||
| − | | <span style="font-size: 16px">[[ TOOL MUSHROOMING]] | + | | <span style="font-size: 16px">[[ TOOL MUSHROOMING]]</span><br /> |
| − | + | | <span style="font-size: 16px">Test tools developed in-house evolve from useful utilities to large and unwieldy automation frameworks </span><br /> | |
|} | |} | ||
| − | <br /> <span style="font-size: 16px">[[Main Page]] </span><br /> <span style="font-size: 16px">[[Test Automation Issues]]</span><br /> <span style="font-size: 16px">[[Test Automation Patterns]]</span><br /> <br /> | + | <br /> <span style="font-size: 16px">[[Main Page]] </span><br /> <span style="font-size: 16px">[[Test Automation Issues]]</span><br /> <span style="font-size: 16px">[[Test Automation Patterns]]</span><br /> <br /> |
| + | [1] Failure Patterns introduced by Michael Stahl </div> | ||
Latest revision as of 13:52, 6 July 2018
Failure patterns show how behaviours that start well can end up as costly failures. These kind of patterns help recognize if an automation project is heading in the wrong direction at a time when countermeasures can still enable a turnaround. Failure patterns are also called "anti-patterns", since they are things that you shouldn't do. In this wiki, they could also be Issues. The table below gives a list of the Failure patterns with a short description.
[1] Failure Patterns introduced by Michael Stahl
| Failure Patterns [1] |
Description |
|---|---|
| FRAMEWORK COMPETITION |
Different teams build different automation frameworks and are not able or willing to consolidate them |
| GOING FOR THE NUMBERS |
The automation team is pushed into automating as many tests as possible while disregarding test robustness |
| THE NIGHT TIME FALLACY |
Targeting "Night runs" can lead to inefficient automation |
| TOOL MUSHROOMING |
Test tools developed in-house evolve from useful utilities to large and unwieldy automation frameworks |