Difference between revisions of "Improve or revive test automation"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"> =<span style="font-size: 16px">What below describes the most pressing problem you have to tackle at the moment?</sp...") |
|||
| Line 10: | Line 10: | ||
# <span style="font-size: 16px">[[ Expectations for automated test execution not met ]](scripts unreliable or too slow, tests cannot run unattended, etc.)</span> | # <span style="font-size: 16px">[[ Expectations for automated test execution not met ]](scripts unreliable or too slow, tests cannot run unattended, etc.)</span> | ||
# <span style="font-size: 16px">[[Maintenance expectations not met]] (undocumented data or scripts, no revision control etc.)</span> | # <span style="font-size: 16px">[[Maintenance expectations not met]] (undocumented data or scripts, no revision control etc.)</span> | ||
| − | <br /> <span style="font-size: 16px">Return to [[Diagnostic]]</span><br /> <br /> <span style="font-size: 16px; line-height: 24px">Notes:</span><br /> <span style="font-size: 16px"> If you find that more than one answer fits your case, start with the most challenging. Once you have resolved it, you should return to this question and tackle the next ones. </span><br /> <br /> <span style="font-size: 16px">If you want to revive test automation you can also just skip to the issue ''[[ STALLED AUTOMATION]]'' to get an overview of possible solving patterns.</span><br /> <br /> <span style="font-size: 16px">Please let us know if there is a category that we have missed - thanks. See [[ | + | <br /> <span style="font-size: 16px">Return to [[Diagnostic]]</span><br /> <br /> <span style="font-size: 16px; line-height: 24px">Notes:</span><br /> <span style="font-size: 16px"> If you find that more than one answer fits your case, start with the most challenging. Once you have resolved it, you should return to this question and tackle the next ones. </span><br /> <br /> <span style="font-size: 16px">If you want to revive test automation you can also just skip to the issue ''[[ STALLED AUTOMATION]]'' to get an overview of possible solving patterns.</span><br /> <br /> <span style="font-size: 16px">Please let us know if there is a category that we have missed - thanks. See [[Feedback]] for how to give feedback on this.</span> |
Revision as of 16:21, 21 August 2018
What below describes the most pressing problem you have to tackle at the moment?
- Lack of support (from management, testers, developers etc.)
- Lack of resources (staff, software, hardware, time etc.)
- Lack of direction (what to automate, which automation architecture to implement etc.)
- Lack of specific knowledge (how to test the Software Under Test (SUT), use a tool, write maintainable automation etc.)
- Management expectations for automation not met (Return On Investment (ROI), behind schedule etc.)
- Expectations for automated test execution not met (scripts unreliable or too slow, tests cannot run unattended, etc.)
- Maintenance expectations not met (undocumented data or scripts, no revision control etc.)
Return to Diagnostic
Notes:
If you find that more than one answer fits your case, start with the most challenging. Once you have resolved it, you should return to this question and tackle the next ones.
If you want to revive test automation you can also just skip to the issue STALLED AUTOMATION to get an overview of possible solving patterns.
Please let us know if there is a category that we have missed - thanks. See Feedback for how to give feedback on this.