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
(Meetings)
m (QA tools)
 
(88 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Quality =
 
= Quality =
  
== Releases ==
 
  
{| border = 1 valign="top" cellpadding="10"
 
! Release
 
! Mer Core
 
! SDK
 
|-
 
| Pre release xx
 
|
 
* Test reports
 
|
 
* Test reports
 
|-
 
| Current release xx
 
|
 
* Test reports
 
|
 
* Test reports
 
|}
 
 
== Processes and test plans ==
 
 
* [[Quality/Terminology|Terminology/Glossary]]
 
 
* [[Quality/Test coverage|Test coverage]]
 
* [[Quality/Test coverage|Test coverage]]
 +
* [[Quality/Metrics|Metrics]]
 
* [[Quality/Test processes|Test processes]]
 
* [[Quality/Test processes|Test processes]]
* [[Quality/Test development|Test development]]
+
* [[Quality/Development|Development]]
 +
* [[Quality/Terminology|Terminology/Glossary]]
  
 
== QA tools ==
 
== QA tools ==
  
 
QA tools used in Mer:
 
QA tools used in Mer:
* [[Quality/QA-tools]]
+
* [[Quality/QA-tools | Tools]]
  
 
HowTo's
 
HowTo's
 +
* [[Quality/Tutorials/Testing_with_SDK_to_VM]]
 
* [[Quality/ExecuteTests|Execute tests]]
 
* [[Quality/ExecuteTests|Execute tests]]
 +
* [[Quality/TestDefinitionHowTo|Writing test-definition XMLs]]
  
 
== ToDo ==
 
== ToDo ==
  
* Plan simple test set for chroot environment
+
1. '''Test automation and tools'''
* Setup test automation for chroot environment (OTS and testrunner-lite should work almost out of the box)
+
# Automatic smoke testing
* Test result reporting (QA-reports, see task [https://bugs.merproject.org/show_bug.cgi?id=244 Mer-244])
+
## Create test automation virtual image ([[Quality/ExecuteTests | HowTo]])
* Integrade testing into updating and release process
+
## Setup test automation environment (Yunta from Jolla is working on this)
** Also for SDK releases?
+
## Create smoke test plan ([[Quality/Test coverage|Test plans]])
* Test management
+
## QA-reports for test result reporting ([https://bugs.merproject.org/show_bug.cgi?id=244 MER-244], phaeron)
* Virtual image testing, maybe nemo images
+
# testrunner-ui refactorin ([https://bugs.merproject.org/show_bug.cgi?id=436 MER-436], timoph)
* Community device pool
+
# TDriver in Qt5 ([https://bugs.merproject.org/show_bug.cgi?id=439 MER-439], Paimen)
 +
# TDriver with QtQuick 2.0 ([https://bugs.merproject.org/show_bug.cgi?id=440 MER-440], Paimen)
 +
# Design to identify test constraints ([https://bugs.merproject.org/show_bug.cgi?id=317 MER-317], not taken)
 +
# Netconsole for debugging, http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt (not taken)
 +
 
 +
2. ''' Test coverage '''
 +
# Create a coverage chart/table for core packages ([[Quality/Test coverage|Test coverage]])
 +
 
 +
3. ''' Mer Dashboard '''
 +
# Mer dashboard ([https://bugs.merproject.org/show_bug.cgi?id=429 Mer-429], kyyberi and lbt)
 +
# http://www.youtube.com/watch?v=urmp-fmjRro
 +
 
 +
4. '''Documentation'''
 +
# Create [[:Category:About]] pages for tools and processes
 +
# Create a documentation how to contribute to the QA tests
 +
 
 +
[https://bugs.merproject.org/buglist.cgi?query_format=advanced&bug_status=NEEDINFO&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=TRIAGEDUPSTREAM&bug_status=REOPENED&product=Mer%20QA List of all bugs and tasks in QA area.]
  
 
== Contact ==
 
== Contact ==
Line 54: Line 52:
 
== Meetings ==
 
== Meetings ==
  
* [http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-12-12.01.html Meeting minutes 2012-04-12]
+
=== Future topics ===
* [http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-04-03-11.00.html Meeting minutes 2012-04-03]
+
 
 +
* Test coverage
 +
 
 +
 
 +
=== Minutes ===
 +
 
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-09-27-12.00.html Meeting minutes 2012-09-27, Status update and QA roles changes]
 +
* [http://epeli.org/mer/mer-qa-meetin-2012-09-13.txt Meeting minutes 2012-09-13, Status update]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-08-09-12.03.html Meeting minutes 2012-08-09, Status update]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-08-02-12.00.html Meeting minutes 2012-08-02, Mer Dashboard]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-07-26-12.00.html Meeting minutes 2012-07-26, OTS replacement]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-07-19-12.00.html Meeting minutes 2012-07-19, Bug metrics and QA ToDo]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-07-12-12.00.html Meeting minutes 2012-07-12, Status update]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-07-05-12.20.html Meeting minutes 2012-07-05, Status update]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-06-21-12.00.html Meeting minutes 2012-06-21, Acceptance criteria for the tools and tests]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-06-14-12.01.html Meeting minutes 2012-06-14, Status update]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-05-31-12.00.html Meeting minutes 2012-05-31, Test automation image]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-05-24-12.00.html Meeting minutes 2012-05-24, QA tools and OBS]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-05-10-12.00.html Meeting minutes 2012-05-10, Status update]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-05-03-12.16.html Meeting minutes 2012-05-03, QA process] and [http://epeli.org/mer/mer-qa-meetin-2012-05-03.txt full log]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-04-26-12.00.html Meeting minutes 2012-04-26, Test constraints and mapping]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-04-19-11.00.html Meeting minutes 2012-04-19, Test package mapping]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-04-12-12.01.html Meeting minutes 2012-04-12, QA process, tools and tests]
 +
* [http://merproject.org/meetings/mer-meeting/2012/mer-meeting.2012-04-03-11.00.html Meeting minutes 2012-04-03, Initial meeting]
  
 
[[Category:QA]]
 
[[Category:QA]]

Latest revision as of 12:38, 8 October 2012

Contents

[edit] Quality

[edit] QA tools

QA tools used in Mer:

HowTo's

[edit] ToDo

1. Test automation and tools

  1. Automatic smoke testing
    1. Create test automation virtual image ( HowTo)
    2. Setup test automation environment (Yunta from Jolla is working on this)
    3. Create smoke test plan (Test plans)
    4. QA-reports for test result reporting (MER-244, phaeron)
  2. testrunner-ui refactorin (MER-436, timoph)
  3. TDriver in Qt5 (MER-439, Paimen)
  4. TDriver with QtQuick 2.0 (MER-440, Paimen)
  5. Design to identify test constraints (MER-317, not taken)
  6. Netconsole for debugging, http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt (not taken)

2. Test coverage

  1. Create a coverage chart/table for core packages (Test coverage)

3. Mer Dashboard

  1. Mer dashboard (Mer-429, kyyberi and lbt)
  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 in QA area.

[edit] Contact

[edit] Meetings

[edit] Future topics

  • Test coverage


[edit] Minutes

Personal tools