Difference between revisions of "OBSCURE MANAGEMENT REPORTS"

From Test Automation Patterns
Jump to navigation Jump to search
m (Topic titles in capital letters)
m (empty lines removed)
 
Line 1: Line 1:
 
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span>
 
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span>
 
=<span style="font-family: Arial; font-size: 16px">'''Issue summary'''</span>=
 
=<span style="font-family: Arial; font-size: 16px">'''Issue summary'''</span>=
<br /> <span style="font-family: Arial; font-size: 16px">Reports from test automation are not very useful to monitor the process and keep management informed </span><br /> <br />  
+
<span style="font-family: Arial; font-size: 16px">Reports from test automation are not very useful to monitor the process and keep management informed </span>  
 
=<span style="font-family: Arial; font-size: 16px">'''Category'''</span>=
 
=<span style="font-family: Arial; font-size: 16px">'''Category'''</span>=
<br /> <span style="font-family: Arial; font-size: 16px">Management</span><br /> <br />  
+
<span style="font-family: Arial; font-size: 16px">Management</span>  
 
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>=
 
=<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>=
<br />
 
 
# <span style="font-family: Arial; font-size: 16px">Test automation reports only if the current tests passed or failed, trends have to be built manually</span>
 
# <span style="font-family: Arial; font-size: 16px">Test automation reports only if the current tests passed or failed, trends have to be built manually</span>
 
# <span style="font-family: Arial; font-size: 16px">It is difficult to get a "big picture" about what parts of the system are OK or have serious problems</span>
 
# <span style="font-family: Arial; font-size: 16px">It is difficult to get a "big picture" about what parts of the system are OK or have serious problems</span>
<br />
 
 
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>=
 
=<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>=
<br /> <span style="font-family: Arial; font-size: 16px">What kind of information is currently delivered by test automation?</span><br /> <span style="font-family: Arial; font-size: 16px">What kind of information does management need?</span><br /> <br />  
+
<span style="font-family: Arial; font-size: 16px">What kind of information is currently delivered by test automation?</span><br /> <span style="font-family: Arial; font-size: 16px">What kind of information does management need?</span>  
 
=<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>=
 
=<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>=
<br /> <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> <span style="font-size: 16px">[[READABLE REPORTS]]: apply this pattern to give your stakeholders the information they need</span><br /> <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> <span style="font-size: 16px">[[LEARN FROM MISTAKES]]: apply this pattern to learn to do better next time!</span><br /> <span style="font-size: 16px">[[SHARE INFORMATION]]: apply this pattern in order to find out what kind of reports are needed</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div>
+
<span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> <span style="font-size: 16px">[[READABLE REPORTS]]: apply this pattern to give your stakeholders the information they need</span><br /> <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> <span style="font-size: 16px">[[LEARN FROM MISTAKES]]: apply this pattern to learn to do better next time!</span><br /> <span style="font-size: 16px">[[SHARE INFORMATION]]: apply this pattern in order to find out what kind of reports are needed</span><br /> <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Issues]] / Back to [[Test Automation Issues]]</span></div>

Latest revision as of 16:50, 7 May 2018

.................................................................................................................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