Revision as of 22:42, 22 June 2011

Quality

This page is for MeeGo Quality Assurance related material.

Projects

For all test reports, see http://qa-reports.meego.com

QA tools

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.

• Meet the team and find our tools
• Participate in development activities. You are most welcome!

The following links provide some basic information on QA tools and their usage.

• Setting up the repositories for installing tools (please note that not all tools are in these repositories yet)
• Test packaging: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
• Autotest-Guide: A guide for setting up automated testing environment. It includes instructions on how to automate test execution and image installations.

Procedures and best practices

• Feature Testability 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.
• Testability Commenting Guide
  • This is a guide for QA contacts about how to comment on feature testability, so as to provide test developers as much information as possible.
• MeeGo Core Test Suites Development Guidelines
  
• MeeGo Core Test Suites Packaging draft
  
• Test plan template -- PROPOSAL, please contribute
• Component Test Plan Template -- WORK IN PROGRESS, please contribute
• Test Case Template -- Updated, ready for approval
• Test Design Process and Guideline -- WORK IN PROGRESS, please contribute
• Test Set Guideline
• Test management overview

Defect tracking

• Defects Management
• Bug Life Cycle and Report Handling/Follow-up Guidelines
• Fields in a bug report
• MeeGo Bug Triage
• MeeGo Bug Triage Stock Answers -- WORK IN PROGRESS, please contribute
• MeeGo Sys-Debug (finding the right component for a report)
• How to report bugs
• Bug Report Access Restrictions
• Bugzilla customized features
• Requests for changes in Bugzilla code/UI itself

Error Management

See the Quality/Error Management subpage.

Compliance Program

MeeGo Compliance Program - the compliance spec (initially)

Contact

• Mailing List: MeeGo-QA
• IRC: Channel #meego-qa on irc.freenode.net

Meetings

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.

See also

• QA Glossary
• Short descriptions for Test Areas/Types
• Quality Considerations / 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

• What is the QA contact expected to do actually?
  • QA contact work with/support/advice/help package maintainers (see Fedora example [[1]] or MeeGo guidelines for maintaining package [[2]]) and other users on QA related issues/questions for component in case.
    • Features ("Once a requirement is integrated, MeeGo QA verifies it by running the corresponding test cases." from [[3]])
      • make testability analysis for features (yes or no value to testability field) and
      • identify "feature acceptance tests" together with product management and package maintainers that could be used at the end as a criteria for feature status to be changed as "VERIFIED".
    • Bugs ("QA Contact or Bug Submitter verifies bug fixing with the "how to re-produce" instructions in the original bug report when the bug is marked as RELEASED - FIXED." from [[4]])
      • facilitate the whole bug life-cycle from QA perspective, including ensure bug report completeness, follow up bugs by providing helpful or required information in timely fashion to accelerate bug fixing and verify the issue after fix is integrated, especially when the original reporter is not responsive or has difficulty to follow the bug up.
      • actively follow-up the bugs. Making sure the bug is attended properly, ping the default assignee or assignee or reporter to get visibility and comments on the progress, triage bugs, verify and close them whenever possible.