Management expectations for automation not met

From Test Automation Patterns
Revision as of 10:57, 3 August 2018 by Dorothy (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
What is the main expectation that the automation hasn't met:

  1. Management expected too much from automation: look up the issue UNREALISTIC EXPECTATIONS
  2. The expected Return on Investment (ROI) has not been achieved. The issue that deals with this is HIGH ROI EXPECTATIONS.
  3. 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.
  4. 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