Page History

...

Similar to “found by/where,” but “how bad”? These metrics help us understand the severity of the issues we encounter. As build quality improves, we would expect to see decreases in the severity of issues identified. A high rate of critical issues identified late in the release cycle would be cause for concern, though it may be expected at an earlier time.

These could roughly be could be sourced from the “Priority” field in JIRA:
– Trivial
– Minor
– Major
– Critical
– Blocker

While “priority” doesn’t map directly to “severity,” it may be a useful proxy. Alternately, we could introduce a label intended to represent severity if we’d like to make that clear.

...

Performance tests tell us “how fast” (and “how expensive”). There are likely many metrics we’d like to we could capture here, and a variety of workloads they could be sourced from.

...

Having this sort of feedback on a build-by-build basis would help us catch regressions early, quantify improvements quickly, and provide a baseline against 3.0 and 3.x.

Metric: Code Coverage (/ other Static Analysis techniques)

...