The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)

Quality

From Mer Wiki
(Difference between revisions)
Jump to: navigation, search
(→‎Future topics)
(→‎Metrics)
Line 3: Line 3:
 
== Metrics ==
 
== Metrics ==
  
−
'''Bugs'''
+
=== Bugs ===
−
* Number of currently open bugs/task in Core. (# of High / Normal / Low and Critical / Major / Normal / Task)
+
 
 +
 
 +
{| border="0" cellspacing="0" cellpadding="2"
 +
| colspan="5" | '''Open bugs and tasks:'''
 +
|-
 +
! Product:
 +
| colspan="4" | Mer Core
 +
|-
 +
! Status:
 +
| colspan="4" | NEEDINFO, UNCONFIRMED, NEW, ASSIGNED, TRIAGEDUPSTREAM, REOPENED
 +
|-
 +
| |
 +
| colspan="2" | '''By priority:'''
 +
| colspan="2" | '''By severity:'''
 +
|-
 +
| || High: || 9 || Critical || 1
 +
|-
 +
| || Normal: || 43 || Major || 4
 +
|-
 +
| || Low: || 86 || Normal || 37
 +
|-
 +
| colspan="3" | || Trivial || 4
 +
|-
 +
| colspan="3" | || Echancement || 1
 +
|-
 +
| colspan="3" | || Task || 96
 +
|-
 +
! Total:
 +
| colspan="4" | 143 (47 bugs and 96 tasks)
 +
|-
 +
|}
 +
 
 +
 
 +
 
 +
 
 
* Metrics for iteration (release) burn-down chart: Number of open bugs/tasks, number of resolved bugs/tasks
 
* Metrics for iteration (release) burn-down chart: Number of open bugs/tasks, number of resolved bugs/tasks
 
* Mean-time to fix a bug / task based on priority, with upper and lower limits
 
* Mean-time to fix a bug / task based on priority, with upper and lower limits

Revision as of 11:41, 18 July 2012

Contents

Quality

Metrics

Bugs

Open bugs and tasks:
Product: Mer Core
Status: NEEDINFO, UNCONFIRMED, NEW, ASSIGNED, TRIAGEDUPSTREAM, REOPENED
By priority: By severity:
High: 9 Critical 1
Normal: 43 Major 4
Low: 86 Normal 37
Trivial 4
Echancement 1
Task 96
Total: 143 (47 bugs and 96 tasks)



  • Metrics for iteration (release) burn-down chart: Number of open bugs/tasks, number of resolved bugs/tasks
  • Mean-time to fix a bug / task based on priority, with upper and lower limits
  • Number of the closed bugs based on status
  • Number of bugs fixed per person

QA Processes

QA tools

QA tools used in Mer:

HowTo's

ToDo

1. Test automation

  1. Automatic smoke testing
    1. Create test automation virtual image (with eat, SSH and static IP)
    2. Setup OTS environment
      1. Create "flasher" for OTS
    3. Create smoke test plan
    4. Test result reporting (QA-reports, see task Mer-244)
  2. Review OTS and how it fits to the BOSS
  3. Design to identify test constraints Mer-317
  4. Netconsole for debugging, http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt

2. Test coverage

  1. Create a coverage chart/table for core packages

3. Mer Dashboard

  1. Mer dashboard Mer-429
  2. http://www.youtube.com/watch?v=urmp-fmjRro

4. Documentation

  1. Create Category:About pages for tools and processes
  2. Create a documentation how to contribute to the QA tests

List of all bugs and tasks related to QA.

Contact

Meetings

Future topics

  • Bug metrics and QA ToDo list (19.7.2012)
  • Test coverage (26.7.2012)

Minutes

Retrieved from "https://wiki.merproject.org/wiki/index.php?title=Quality&oldid=2104"
Personal tools