Difference between revisions of "Management expectations for automation not met"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 16px">What is the main expectation that the automation hasn't met:</span><br /> <br /> # <...") |
m |
||
| Line 5: | Line 5: | ||
# <span style="font-size: 16px">The automation project is not on schedule (development of automation is too slow). The issue that suggests possible patterns to solve this problem is ''[[SCHEDULE SLIP]].''</span> | # <span style="font-size: 16px">The automation project is not on schedule (development of automation is too slow). The issue that suggests possible patterns to solve this problem is ''[[SCHEDULE SLIP]].''</span> | ||
# <span style="font-size: 16px">The reports from automation are too difficult to analyse. Look up the issue ''[[OBSCURE MANAGEMENT REPORTS]]'' if management finds the reports unsatisfactory, or ''[[INEFFICIENT FAILURE ANALYSIS]]'' if reports on failures aren't helpful.</span> | # <span style="font-size: 16px">The reports from automation are too difficult to analyse. Look up the issue ''[[OBSCURE MANAGEMENT REPORTS]]'' if management finds the reports unsatisfactory, or ''[[INEFFICIENT FAILURE ANALYSIS]]'' if reports on failures aren't helpful.</span> | ||
| − | <br /> <br /> <span style="background-color: #ffffff; font-size: 16px">Return to [[Improve or revive test | + | <br /> <br /> <span style="background-color: #ffffff; font-size: 16px">Return to [[Improve or revive test Automation]]</span><br /> <br /> <span style="background-color: #ffffff; font-size: 16px">B10</span></div> |
Revision as of 14:27, 25 June 2018
What is the main expectation that the automation hasn't met:
Return to Improve or revive test Automation
B10
- Management expected too much from automation: look up the issue UNREALISTIC EXPECTATIONS
- The expected Return on Investment (ROI) has not been achieved. The issue that deals with this is HIGH ROI EXPECTATIONS.
- The automation project is not on schedule (development of automation is too slow). The issue that suggests possible patterns to solve this problem is SCHEDULE SLIP.
- The reports from automation are too difficult to analyse. Look up the issue OBSCURE MANAGEMENT REPORTS if management finds the reports unsatisfactory, or INEFFICIENT FAILURE ANALYSIS if reports on failures aren't helpful.
Return to Improve or revive test Automation
B10