Ubuntu

Quality Metrics

Registered by Gema Gomez on 2011-09-30

A first set of metrics are to be put in place during Precise. This session is to discuss about code coverage and test escape analysis.

Blueprint information

Status:: Complete

Approver:: Pete Graner

Priority:: Essential

Drafter:: Gema Gomez

Direction:: Approved

Assignee:: Canonical Platform QA Team

Definition:: Approved

Series goal:: Accepted for quantal

Implementation:: Informational

Milestone target:: quantal-alpha-3

Started by: Gema Gomez on 2012-04-30

Completed by: Gema Gomez on 2012-04-30

Related branches

Related bugs

Sprints

uds-p

Whiteboard

Decide which metrics are the most appropriate to start with and start tracking them, publish results to management and the community to gain momentum and enable people to see what their contributions actually contribute to the overall quality of Ubuntu

* Coverage (conditional, functional)

The kernel has been instrumented with gcov before, some example results to be found here: http://reports.qa.ubuntu.com/reports/ogasawara/gcov-isos/
* Defects
Define a test escape analysis strategy during this cycle.

Actions
* Investigate how to instrument Ubuntu (for coverage) and decide which tools are the most appropriate
* Set up a web/dashboard for publishing results
* Determine what packages to instrument (measure coverage for)
* Determine which information is required for defect analysis and convince the bug-control team to provide us with it

KES: 20120710 - move workitems to separate section, Work Items in wrong section triggering script error.

(?)

Work Items

Work items:
[gema] Investigate how to instrument Ubuntu (for coverage): DONE
[gema] Determine what packages to instrument (measure coverage for): POSTPONED
[patrickmwright] Add coverage results to Jenkins: POSTPONED
[hggdh2] Determine which information is required for defect analysis (only for the packages on the CD) and convince the bug-control team to provide us with it: POSTPONED