OBSCURE MANAGEMENT REPORTS

From Test Automation Patterns
Revision as of 08:57, 5 April 2018 by Cathal (talk | contribs) (Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues

Issue summary


Reports from test automation are not very useful to monitor the process and keep management informed

Category


Management

Examples


  1. Test automation reports only if the current tests passed or failed, trends have to be built manually
  2. It is difficult to get a "big picture" about what parts of the system are OK or have serious problems


Questions


What kind of information is currently delivered by test automation?
What kind of information does management need?

Resolving Patterns


Most recommended:
READABLE REPORTS: apply this pattern to give your stakeholders the information they need

Other useful patterns:
LEARN FROM MISTAKES: apply this pattern to learn to do better next time!
SHARE INFORMATION: apply this pattern in order to find out what kind of reports are needed

.................................................................................................................Main Page / Back to Management Issues / Back to Test Automation Issues