(→See also) |
|||
| Line 5: | Line 5: | ||
== Projects == | == Projects == | ||
| - | For all test reports | + | For all test reports see [http://qa-reports.meego.com http://qa-reports.meego.com] |
{| border = 1 valign="top" | {| border = 1 valign="top" | ||
| Line 84: | Line 84: | ||
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet) | * [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet) | ||
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution. | * [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution. | ||
| - | * [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions | + | * [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations. |
== Procedures and best practices == | == Procedures and best practices == | ||
| Line 91: | Line 91: | ||
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist. | ** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist. | ||
* [[Quality/Testability-commenting|Testability Commenting Guide]] | * [[Quality/Testability-commenting|Testability Commenting Guide]] | ||
| - | ** This is a guide for QA contacts about how to comment on feature testability | + | ** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers. |
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] <br> | *[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] <br> | ||
*[[MeeGo Core Test Suites Packaging draft]] <br> | *[[MeeGo Core Test Suites Packaging draft]] <br> | ||
| Line 127: | Line 127: | ||
== Meetings == | == Meetings == | ||
| - | General QA Meetings are held weekly on Tuesdays 07:00 UTC | + | General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. [[Quality/Meetings|Click here for more information.]] |
| - | QA Tools meetings are held weekly on Tuesdays 08:00 UTC | + | QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. [[Quality/QA-tools/Meetings|Click here for more information.]] |
| - | For information on triaging meetings for specific areas | + | For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]]. |
== See also == | == See also == | ||
| Line 138: | Line 138: | ||
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]] | * [[/Test_areas_and_types | Short descriptions for Test Areas/Types]] | ||
* [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]] | * [[Quality/Plans/Quality-considerations|Quality Considerations / Testing Quality Characteristics]] | ||
| - | ** Some ideas around testing quality characteristics | + | ** Some ideas around testing quality characteristics hopefully helping you identify what kind of things could be checked from applications - can be used as a frame to define test considerations – as a set of logical test cases - for applications targeting to run on MeeGo. |
== Questions and Answers == | == Questions and Answers == | ||
Contents |
This page is for MeeGo Quality Assurance related material.
For all test reports see http://qa-reports.meego.com
| Release | Core OS | Handset UX | Tablet UX | Netbook UX | SDK | In Vehicle Infotainment |
|---|---|---|---|---|---|---|
| Release 1.3 |
|
|
| |||
| Release 1.2 |
|
|
|
Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
The following links provide some basic information on QA tools and their usage.
See the Quality/Error Management subpage.
MeeGo Compliance Program - the compliance spec (initially)
General QA Meetings are held weekly on Tuesdays 07:00 UTC in the channel #meego-meeting on irc.freenode.net. Click here for more information.
QA Tools meetings are held weekly on Tuesdays 08:00 UTC in the channel #meego-meeting2 on irc.freenode.net. Click here for more information.
For information on triaging meetings for specific areas click here.