Quality

Quality

Metrics

Burn-down chart:
Release	Changed packages	Added packages	Fixes	Bugs/tasks reported*	Bugs/tasks resolved*
0.20120209.1	67	0	11	105	39
0.20120315.1	36	0	9	27	15
0.20120405.1	13	2	1	36	2
0.20120419.2	14	4	13	30	12
0.20120517.1	15	2	18	9	19
0.20120614.1	24	9	16	38	13
Total:	169	17	68	245	100

(*) From Bugzilla, other values are from releases changelogs

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)

Closed bugs:
Product:	Mer Core
Status:	RESOLVED, RELEASED, VERIFIED, CLOSED
	By resolution:
	Fixed:	114
	Dupllicate:	6
	Invalid:	4
	By Assignee:
	Sage	39
	not-taken	31
	need-triage	22
	Stskeeps	14
	lbt	6
	letters.random13	4
	arnaud	3
	Martin Brook	2
	Robin	2
	Benjamin Federau	1
Total:	124 (51 bugs and 71 tasks)

Mean-time of fixing bugs/tasks, [days]
Product:	Mer Core
Status:	RESOLVED, RELEASED, VERIFIED, CLOSED
	Priority:	Mean-time:	Min:	Max:	Bugs
	High:	22.2	0.3	81.5
	Normal:	55.3	2.7	136.7
	Low:	-	-	-
	Undecided:	11.5	0.0	49.0
Tasks
	High:	46.1	0.1	108.2
	Normal:	39.1	7.0	126.9
	Low:	37.4	9.3	97.0
	Undecided:	20.4	0.0	80.0

Updated on 18.07.2012

• Mean-time to fix a bug / task based on priority, with upper and lower limits

QA Processes

• Terminology/Glossary
• Test coverage
• Test processes
• Development

QA tools

QA tools used in Mer:

• Tools

HowTo's

• Execute tests
• Writing test-definition XMLs

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

• Mailing lists
• IRC: Channel #mer on irc.freenode.net

Meetings

Future topics

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

Minutes

• Meeting minutes 2012-07-12, Status update
• Meeting minutes 2012-07-05, Status update
• Meeting minutes 2012-06-21, Acceptance criteria for the tools and tests
• Meeting minutes 2012-06-14, Status update
• Meeting minutes 2012-05-31, Test automation image
• Meeting minutes 2012-05-24, QA tools and OBS
• Meeting minutes 2012-05-10, Status update
• Meeting minutes 2012-05-03, QA process and full log
• Meeting minutes 2012-04-26, Test constraints and mapping
• Meeting minutes 2012-04-19, Test package mapping
• Meeting minutes 2012-04-12, QA process, tools and tests
• Meeting minutes 2012-04-03, Initial meeting