Difference between revisions of "Test Automation Issues"
Jump to navigation
Jump to search
Failure Patterns were brought to our attention by Michael Stahl at a STAR conference. There is now also an ebook about them (see References).
We are very grateful to be allowed to add them to our collection.
Main Page
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"> | <div id="content_view" class="wiki" style="display: block"> | ||
| − | =<span style="font-size: 16px">What is an Issue?</span>= | + | =<span style="font-size: 16px">'''What is an Issue?'''</span>= |
<span style="font-size: 16px">An ''Issue'' is a problem that testers and/or test automators encounter when trying to do test automation. They are things that take longer than they should, that hold you back in what you want to automate, or that are just too much trouble - isn't there an easier way? In many cases, yes there is - these are the test automation patterns.</span><br /> <span style="font-size: 16px">An ''Issue'' can also be a task that has to be done when automating and for this case there are also test automation patterns to help execute the task as efficiently as possible.</span><br /> <br /> <span style="font-size: 16px">In this wiki, we show ''ISSUES'' in ''ITALIC CAPS'', where we can format it (haven't figured out how to make a page title italic!)</span> | <span style="font-size: 16px">An ''Issue'' is a problem that testers and/or test automators encounter when trying to do test automation. They are things that take longer than they should, that hold you back in what you want to automate, or that are just too much trouble - isn't there an easier way? In many cases, yes there is - these are the test automation patterns.</span><br /> <span style="font-size: 16px">An ''Issue'' can also be a task that has to be done when automating and for this case there are also test automation patterns to help execute the task as efficiently as possible.</span><br /> <br /> <span style="font-size: 16px">In this wiki, we show ''ISSUES'' in ''ITALIC CAPS'', where we can format it (haven't figured out how to make a page title italic!)</span> | ||
| − | =<span style="font-size: 16px">Typical test automation issues</span>= | + | =<span style="font-size: 16px">'''Typical test automation issues'''</span>= |
<span style="font-size: 16px">The issues that testers have to face when they tackle test automation are manifold. Some are technical in nature, such as ''[[ INEFFICIENT FAILURE ANALYSIS]]'' or ''[[HARD-TO-AUTOMATE]].''</span><br /> <br /> <span style="font-size: 16px">However, one of the main reasons for failure is to concentrate exclusively on the technical aspects. Other issues are related to the way you work, such as ''[[ LATE TEST CASE DESIGN]]'', or when automation seems to get off to a good start, but then grinds to a halt, ''[[STALLED AUTOMATION]]''. Others are Management Issues, such as ''[[HIGH ROI EXPECTATIONS]]''.</span><br /> <span style="font-size: 16px">Some issues may arise due to either technical or management problems.</span> | <span style="font-size: 16px">The issues that testers have to face when they tackle test automation are manifold. Some are technical in nature, such as ''[[ INEFFICIENT FAILURE ANALYSIS]]'' or ''[[HARD-TO-AUTOMATE]].''</span><br /> <br /> <span style="font-size: 16px">However, one of the main reasons for failure is to concentrate exclusively on the technical aspects. Other issues are related to the way you work, such as ''[[ LATE TEST CASE DESIGN]]'', or when automation seems to get off to a good start, but then grinds to a halt, ''[[STALLED AUTOMATION]]''. Others are Management Issues, such as ''[[HIGH ROI EXPECTATIONS]]''.</span><br /> <span style="font-size: 16px">Some issues may arise due to either technical or management problems.</span> | ||
| − | =<span style="font-size: 16px">Classification of Issues:</span>= | + | =<span style="font-size: 16px">'''Classification of Issues:'''</span>= |
<span style="font-size: 16px">We classify the issues into the following categories:</span><br /> | <span style="font-size: 16px">We classify the issues into the following categories:</span><br /> | ||
| − | + | * <span style="font-size: 16px">''[[Process Issues]]'': the way we work with automated tests and tools</span> | |
| − | + | * <span style="font-size: 16px">''[[Management Issues]]'': issues of management, staffing, objectives (need time, money or people to fix)</span> | |
| − | + | * <span style="font-size: 16px">''[[Design Issues]]'': testware architecture, including maintainability</span> | |
| − | + | * <span style="font-size: 16px">''[[Execution Issues]]'': the running of tests in their automated form</span> | |
| − | <br /> <span style="font-size: 16px">Within each category the issues are listed alphabetically.</span><br /> <br /> <span style="font-size: 16px">The [[Test Automation Issues Mind Map]] shows an overview of the specific Test Automation Issues.</span><br /> <br /> <span style="font-size: 16px">Note that [Failure Patterns]] are also a kind of issue because they describe behaviours that, if not recognized in time, can compromize even apparently successful test automation projects. </span><br /> <span style="font-size: 16px">Failure Patterns were brought to our attention by Michael Stahl at STAR | + | <br /> <span style="font-size: 16px">Within each category the issues are listed alphabetically.</span><br /> <br /> |
| + | |||
| + | <span style="font-size: 16px">The [[Test Automation Issues Mind Map]] shows an overview of the specific Test Automation Issues.</span><br /> <br /> | ||
| + | |||
| + | <span style="font-size: 16px">Note that [[Failure Patterns]] are also a kind of issue because they describe behaviours that, if not recognized in time, can compromize even apparently successful test automation projects. They are also referred to as "anti-patterns". </span><br /> <span style="font-size: 16px">Failure Patterns were brought to our attention by Michael Stahl at a STAR conference. There is now also an ebook about them (see [[References]]).</span><br /> <span style="font-size: 16px">We are very grateful to be allowed to add them to our collection. </span><br /> <br /> <span style="font-size: 16px">[[Main Page]]</span></div> | ||
Latest revision as of 01:51, 11 March 2021
What is an Issue?
An Issue is a problem that testers and/or test automators encounter when trying to do test automation. They are things that take longer than they should, that hold you back in what you want to automate, or that are just too much trouble - isn't there an easier way? In many cases, yes there is - these are the test automation patterns.
An Issue can also be a task that has to be done when automating and for this case there are also test automation patterns to help execute the task as efficiently as possible.
In this wiki, we show ISSUES in ITALIC CAPS, where we can format it (haven't figured out how to make a page title italic!)
Typical test automation issues
The issues that testers have to face when they tackle test automation are manifold. Some are technical in nature, such as INEFFICIENT FAILURE ANALYSIS or HARD-TO-AUTOMATE.
However, one of the main reasons for failure is to concentrate exclusively on the technical aspects. Other issues are related to the way you work, such as LATE TEST CASE DESIGN, or when automation seems to get off to a good start, but then grinds to a halt, STALLED AUTOMATION. Others are Management Issues, such as HIGH ROI EXPECTATIONS.
Some issues may arise due to either technical or management problems.
Classification of Issues:
We classify the issues into the following categories:
- Process Issues: the way we work with automated tests and tools
- Management Issues: issues of management, staffing, objectives (need time, money or people to fix)
- Design Issues: testware architecture, including maintainability
- Execution Issues: the running of tests in their automated form
Within each category the issues are listed alphabetically.
The Test Automation Issues Mind Map shows an overview of the specific Test Automation Issues.
Failure Patterns were brought to our attention by Michael Stahl at a STAR conference. There is now also an ebook about them (see References).
We are very grateful to be allowed to add them to our collection.
Main Page