INSUFFICIENT METRICS

From Test Automation Patterns
Jump to: navigation, search
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues

Issue Summary

Few or no metrics are collected or not consistently. Collection is cumbersome.

Category

Process

Examples

  1. Metrics are collected from different systems and have to be consolidated manually.
  2. The collected metrics are not the metrics that are needed by management.
  3. Metrics can only be collected after they have lost most of their importance.

Questions

What metrics are collected?
Which metrics does management need?
Who collects the metrics? When?
In what form are they saved?
Can the collection and/or presentation of the metrics be automated?

Resolving Patterns

Most recommended:

  • SHARE INFORMATION: This pattern is important if you do not really know what metrics are needed (management, development, maintenance etc.)
  • AUTOMATE THE METRICS: Apply this pattern if you need consistent and reliable metrics. It is most necessary for large testing efforts and not only for automation. For small projects it could become an overkill


Other useful patterns:

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