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
(Quality)
(Metrics)
Line 26: Line 26:
 
* Number of currently open bugs/task in Core. (# of High / Normal / Low and Critical / Major / Normal / Task)
 
* Number of currently open bugs/task in Core. (# of High / Normal / Low and Critical / Major / Normal / Task)
 
* 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
+
* Mean-time to fix a bug / task based on priority, with upper and lower limits
  
 
== QA Processes ==
 
== QA Processes ==

Revision as of 11:49, 16 July 2012

Contents

Quality

Releases

Release Mer Core SDK
Pre release xx
  • Test reports
  • Test reports
Current release xx
  • Test reports
  • Test reports


Metrics

  • Number of currently open bugs/task in Core. (# of High / Normal / Low and Critical / Major / Normal / Task)
  • 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

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 simple tests (look from home:esmietti:QA:Tests)
    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. Mer Dashboard

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

3. Documentation

  1. Create Category:About pages for tools and processes
  2. Gather bug metrics and reports them to wiki and QA meeting
  3. Create a coverage chart/table for core packages
  4. Create a documentation how to contribute to the QA tests

Contact

Meetings

Future topics

  • Bug metrics
  • QA ToDo list

Minutes

Personal tools