Revision as of 12:58, 17 July 2012 (view source) Esmietti (Talk | contribs) (→‎Quality) ← Older edit		Revision as of 12:59, 17 July 2012 (view source) Esmietti (Talk | contribs) (→‎Quality) Newer edit →
Line 3:		Line 3:
	== Metrics ==		== Metrics ==
−	* [[Quality/BugMetrics| Bug Metrics]]	+	'''Bugs'''
		+	* 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
		+	* Number of the closed bugs based on status
		+	* Number of bugs fixed per person
	== QA Processes ==		== QA Processes ==

---

Revision as of 12:59, 17 July 2012

Contents 1 Quality 1.1 Metrics 1.2 QA Processes 1.3 QA tools 1.4 ToDo 1.5 Contact 1.6 Meetings 1.6.1 Future topics 1.6.2 Minutes

Quality

Metrics

Bugs

• 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
• Number of the closed bugs based on status
• Number of bugs fixed per person

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 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

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

Meetings

Future topics

• Bug metrics
• QA ToDo list

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