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
(Minutes)
(ToDo)
Line 39: Line 39:
 
== ToDo ==
 
== ToDo ==
  
* Automatic smoke testing
+
1. '''Test automation'''
** Create test automation virtual image (with eat, SSH and static IP)
+
# Automatic smoke testing
** Setup OTS environment
+
## Create test automation virtual image (with eat, SSH and static IP)
*** Create "flasher" for OTS
+
## Setup OTS environment
** Create simple tests (look from home:esmietti:QA:Tests)
+
### Create "flasher" for OTS
** Test result reporting (QA-reports, see task [https://bugs.merproject.org/show_bug.cgi?id=244 Mer-244])
+
## Create simple tests (look from home:esmietti:QA:Tests)
* netconsole for debugging, http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt  
+
## Test result reporting (QA-reports, see task [https://bugs.merproject.org/show_bug.cgi?id=244 Mer-244])
* Design to identify test constraints [https://bugs.merproject.org/show_bug.cgi?id=317 Mer-317]
+
# Review OTS and how it fits to the BOSS
* Create [[:Category:About]] pages for tools and processes
+
# Design to identify test constraints [https://bugs.merproject.org/show_bug.cgi?id=317 Mer-317]
* Review OTS and how it fits to the BOSS
+
# netconsole for debugging, http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt  
* Gather bug metrics and reports them to wiki and QA meeting
+
 
* Mer dashboard [https://bugs.merproject.org/show_bug.cgi?id=429 Mer-429]
+
2. ''' Mer Dashboard '''
* Create a coverage chart/table for core packages
+
# Mer dashboard [https://bugs.merproject.org/show_bug.cgi?id=429 Mer-429]
* Create a documentation how to contribute to the QA tests
+
 
 +
3. '''Documentation'''
 +
# Create [[:Category:About]] pages for tools and processes
 +
# Gather bug metrics and reports them to wiki and QA meeting
 +
# Create a coverage chart/table for core packages
 +
# Create a documentation how to contribute to the QA tests
  
 
== Contact ==
 
== Contact ==

Revision as of 11:40, 16 July 2012

Contents

Quality

Releases

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

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

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