Quality/Triageteam Assignee

2011-07-15T03:02:28Z

Fan: /* Reference */

Quality

2011-07-15T02:53:05Z

Fan: /* Defect tracking */

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [http://wiki.meego.com/Quality/getting-started How Can I Contribute]
== Projects ==

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

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
* [[/meego core feature/1.3 | Core Requirements]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/Plans/1_2_Handset_UX_test_plan MeeGo HandSet UX Test Plan]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/1.2NetbookTestPlan 1.2 SW Update Test Plan]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Meet the team and find our tools]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[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/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 ==

* [[Quality/Plans/Testability-checklist|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.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** 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]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/triageteam_assignee | Process to deal with bugs assigned to triageteam@meego.bugs]]
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization Features]]
* [https://gitorious.org/meego-bugzilla Bugzilla Codebase repository] (move not finished yet)
* [[/MeeGoBugzillaRequestProcess|How to requests changes in Bugzilla code/UI itself]]

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa 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. [[Quality/Meetings|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. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|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 [[http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility ]] or MeeGo guidelines for maintaining package [[http://wiki.meego.com/Packaging/Guidelines#Maintaining_a_Package ]]) 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 [[https://meego.com/developers/requirements ]])
**** 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 [[http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling ]])
**** 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.

[[Category:QA]]

Quality

2011-07-15T02:52:34Z

Fan: /* Defect tracking */

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [http://wiki.meego.com/Quality/getting-started How Can I Contribute]
== Projects ==

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

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
* [[/meego core feature/1.3 | Core Requirements]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/Plans/1_2_Handset_UX_test_plan MeeGo HandSet UX Test Plan]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/1.2NetbookTestPlan 1.2 SW Update Test Plan]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Meet the team and find our tools]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[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/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 ==

* [[Quality/Plans/Testability-checklist|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.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** 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]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [[/Quality/triageteam_assignee Process to deal with bugs assigned to triageteam@meego.bugs]]
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization Features]]
* [https://gitorious.org/meego-bugzilla Bugzilla Codebase repository] (move not finished yet)
* [[/MeeGoBugzillaRequestProcess|How to requests changes in Bugzilla code/UI itself]]

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa 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. [[Quality/Meetings|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. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|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 [[http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility ]] or MeeGo guidelines for maintaining package [[http://wiki.meego.com/Packaging/Guidelines#Maintaining_a_Package ]]) 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 [[https://meego.com/developers/requirements ]])
**** 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 [[http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling ]])
**** 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.

[[Category:QA]]

Quality/triageteam assignee

2011-07-15T02:45:17Z

Fan: moved Quality/triageteam assignee to Quality/Triageteam Assignee

#REDIRECT [[Quality/Triageteam Assignee]]

Quality/Triageteam Assignee

2011-07-15T02:45:17Z

Fan: moved Quality/triageteam assignee to Quality/Triageteam Assignee

== Why triageteam@meego.bugs account?==
* Bug assignees have the requirement to feedback that the bugs are assigned to wrong person, and they have no idea who should be the right owner.
* Usually no single person has the bandwidth and capability to analyze all of the bugs which are assigned to this account, especially there are some system level bugs which need deep analysis in MeeGo context.

== How bugs are assigned to triageteam@meego.bugs account?==
* "triageteam@meego.bugs" is not supposed to be set as default assignee of any component in bugzilla.
* When developers believe the bugs are assigned to wrong person, and they have no idea who should own the bugs, they will assign bugs to triageteam@meego.bugs account

== Actions to facilitate the lifecycle for bugs assigned to triageteam@meego.bugs ==
* Bugs assigned to triageteam@meego.bugs will be published to wiki so that people have direct visibility of those bugs.
* Bug triage team will try their best to re-triage the bugs
* Bug list will be sent to meego-dev mailing list regularly to see if community developers are interested in taking those bugs
* The target is to get the bugs triaged to a named assignee in 5 business days, and if not, the bugs will be escalated to program managers to help find out the assignee.
* Bugs assigned to triageteam@meego.bugs will be scrubbed every week until they are re-assigned

==Bug List==
{{#bugzilla:
|columns=id,priority,status,to,summary
|to=triageteam@meego.bugs
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
|sort=id
|order=asec
}}

== Contact ==
* [mailto:fan.zhao@intel.com Fan Zhao]
* [mailto:jiex.zhou@intel.com Jie Zhou]
== Reference ==
* [http://wiki.meego.com/Quality/Bugtriage Bug Triage Process]

Quality/Bugtriage

2011-07-14T02:32:50Z

Fan: /* Bug Triage Process */

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report completeness
** Analyze and move bug to proper component if needed
** Set Assignee of bug report (via "Assigned to" field) to proper bug owner
** Assign bug to packages listed in "MeeGo Distribution Packages" product whenever possible (apply for new incoming bug reports for version 1.3 ONLY at this moment)
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Resolve obvious invalid, duplication, won’t fix bugs etc.
** Forward bugs in upstream components to [[Quality/UpstreamBugTrackers | upstream bugtrackers]] and adding the upstream URL to the URL field of the report, if applicable

* Bug Triage Team
** A small team works on bug triage, could be experienced developer, distro engineer or QA
** Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]].

== Bug Triage Process ==
* Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
* Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
* Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
* Bug assignees accept bug reports by setting target milestones for triaged bug reports
* [http://meego.com/about/governance/program-office Program Managers] host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:

[[File:bug_triage_2.PNG]]

== MeeGo Bug Triage Guide ==
Check the [[Quality/Bugtriage_Guide|Triage Guide]] that explains good practices when triaging bug reports.

== MeeGo Bug Triage Team ==
{|cellspacing="0" border="1"
!|MeeGo Bug Triage Team
!|Member
|-
| MeeGo Core OS Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ares2012 Jason Zhou], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Handset UX Triage || [http://meego.com/users/fan Fan Zhao], Cathy Li, [http://meego.com/users/srikanthyarlagadda Srikanth Yarlagadda], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || Daniel Tao,[http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo Tablet UX Triage || Daniel Tao, [http://meego.com/users/yanglei Lei Yang], Cathy Li
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
|-
| MeeGo SDK Triage || [http://meego.com/users/ionutgavaz Ionut Gavaz], Jackie Wu, [http://meego.com/users/edmondas Edmondas Girkantas], Azadeh Karimian, Max Yu, Juha Peisanen
|-
| MCTS (MeeGo Core System Testing) Triage || Jeff Zheng,[http://meego.com/users/iekku Iekku Huttunen]
|}

=== MeeGo Bug Triage Meetings ===

* MeeGo Core Bug Triage
** Time: Every Monday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Handset Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
** Time: TBD
* MeeGo Translation Bug Triage
** Time: TBD
* MeeGo SDK Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]

Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net].

* MeeGo Tablet Bug Triage
** Time: Every Thursday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** IRC channel '''#meego-meeting2''' on [http://freenode.net irc.freenode.net]

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

* [[CoreBugTriageMinutesArchive|MeeGo Core Bug Triage Meeting Minutes Archive]]
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]]
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]]
* [[SDKBugTriageMinutesArchive|MeeGo SDK Bug Triage Meeting Minutes Archive]]

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo!

== Other references ==
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]

[[Category:QA]]

Quality

2011-07-14T02:25:38Z

Fan: /* Defect tracking */

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [http://wiki.meego.com/Quality/getting-started How Can I Contribute]
== Projects ==

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

{| border = 1 valign="top"
! Release
! Core OS
! Handset UX
! Tablet UX
! Netbook UX
! SDK
! In Vehicle Infotainment
|-
| Release 1.3
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.3/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
* [[/meego core feature/1.3 | Core Requirements]]
|
* [[Quality/Plans/Handset UX test plan|MeeGo HandSet UX Test Plan]]
* [http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests Test Suite]
* [http://qa-reports.meego.com/1.3/Handset Handset Test Reports]
|
* Tablet UX Test Plan
* Tablet UX Test Suite
* [http://qa-reports.meego.com/1.3/Tablet Tablet Test Reports]
|
* Test Plan
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.3/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.3/SDK SDK Test Reports]
|
* [[/Plans/IVI Test Plan | MeeGo IVI Test Plan]]
* IVI Test Suite
* [http://qa-reports.meego.com/1.3/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|-
| Release 1.2
|
* [[/Plans/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [http://qa-reports.meego.com/1.2/Core Core Test Reports]
* [[Quality/CoreQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/Plans/1_2_Handset_UX_test_plan MeeGo HandSet UX Test Plan]
* [[Quality/TestSuite/handset-test-suite|Test Suite]]
* [http://qa-reports.meego.com/1.2/Handset Handset Test Reports]
* [[Quality/HandsetQualityMetrics|Quality Metrics]]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/Tablet Tablet Test Reports]
* [[Quality/TabletQualityMetrics | Quality Metrics]]
|
* [http://wiki.meego.com/Quality/1.2NetbookTestPlan 1.2 SW Update Test Plan]
* [[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]]
* [http://qa-reports.meego.com/1.2/Netbook Netbook Test Reports]
|
* [[SDKTestPlan|Test Plan]]
* Test Suite
* [http://qa-reports.meego.com/1.2/SDK SDK Test Reports]
|
* Test Plan
* Test Suite
* [http://qa-reports.meego.com/1.2/IVI IVI Test Reports]
* [[Quality/IVIQualityMetrics | Quality Metrics]]
|}

== QA tools ==

Quality assurance tools are developed to ensure MeeGo SW quality. They are developed and maintained by QA tools team.
* [[Quality/QA-tools|Meet the team and find our tools]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[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/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 ==

* [[Quality/Plans/Testability-checklist|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.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** 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]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

* [[/defects | Defects Management]]
* [[/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Report Handling/Follow-up Guidelines]]
* [[/Bugzilla_Fields|Fields in a bug report]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [[/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]] -- WORK IN PROGRESS, please contribute
* [[/SysDebug | MeeGo Sys-Debug]] (finding the right component for a report)
* [http://wiki.meego.com/Quality/triageteam_assignee Process to deal with bugs assigned to triageteam@meego.bugs]
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|MeeGo Bugzilla Customization Features]]
* [https://gitorious.org/meego-bugzilla Bugzilla Codebase repository] (move not finished yet)
* [[/MeeGoBugzillaRequestProcess|How to requests changes in Bugzilla code/UI itself]]

== Compliance Program ==
[[Quality/Compliance | MeeGo Compliance Program]] - the compliance spec (initially)

== Contact ==

* Mailing List: [http://lists.meego.com/listinfo/meego-qa 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. [[Quality/Meetings|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. [[Quality/QA-tools/Meetings|Click here for more information.]]

For information on triaging meetings for specific areas [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|click here]].

== See also ==

* [[/Glossary | QA Glossary ]]
* [[/Test_areas_and_types | Short descriptions for Test Areas/Types]]
* [[Quality/Plans/Quality-considerations|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 [[http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility ]] or MeeGo guidelines for maintaining package [[http://wiki.meego.com/Packaging/Guidelines#Maintaining_a_Package ]]) 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 [[https://meego.com/developers/requirements ]])
**** 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 [[http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling ]])
**** 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.

[[Category:QA]]

Quality/Bugtriage

2011-07-14T01:58:11Z

Fan: /* Bug Triage Process */

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report completeness
** Analyze and move bug to proper component if needed
** Set Assignee of bug report (via "Assigned to" field) to proper bug owner
** Assign bug to packages listed in "MeeGo Distribution Packages" product whenever possible (apply for new incoming bug reports for version 1.3 ONLY at this moment)
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Resolve obvious invalid, duplication, won’t fix bugs etc.
** Forward bugs in upstream components to [[Quality/UpstreamBugTrackers | upstream bugtrackers]] and adding the upstream URL to the URL field of the report, if applicable

* Bug Triage Team
** A small team works on bug triage, could be experienced developer, distro engineer or QA
** Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]].

== Bug Triage Process ==
* Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
* Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
* Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
* Bug assignees accept bug reports by setting target milestones for triaged bug reports
* [http://meego.com/about/governance/program-office Program Managers] host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:
[[File:bug_triage_2.PNG]]

== MeeGo Bug Triage Guide ==
Check the [[Quality/Bugtriage_Guide|Triage Guide]] that explains good practices when triaging bug reports.

== MeeGo Bug Triage Team ==
{|cellspacing="0" border="1"
!|MeeGo Bug Triage Team
!|Member
|-
| MeeGo Core OS Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ares2012 Jason Zhou], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Handset UX Triage || [http://meego.com/users/fan Fan Zhao], Cathy Li, [http://meego.com/users/srikanthyarlagadda Srikanth Yarlagadda], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || Daniel Tao,[http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo Tablet UX Triage || Daniel Tao, [http://meego.com/users/yanglei Lei Yang], Cathy Li
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
|-
| MeeGo SDK Triage || [http://meego.com/users/ionutgavaz Ionut Gavaz], Jackie Wu, [http://meego.com/users/edmondas Edmondas Girkantas], Azadeh Karimian, Max Yu, Juha Peisanen
|-
| MCTS (MeeGo Core System Testing) Triage || Jeff Zheng,[http://meego.com/users/iekku Iekku Huttunen]
|}

=== MeeGo Bug Triage Meetings ===

* MeeGo Core Bug Triage
** Time: Every Monday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Handset Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
** Time: TBD
* MeeGo Translation Bug Triage
** Time: TBD
* MeeGo SDK Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]

Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net].

* MeeGo Tablet Bug Triage
** Time: Every Thursday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** IRC channel '''#meego-meeting2''' on [http://freenode.net irc.freenode.net]

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

* [[CoreBugTriageMinutesArchive|MeeGo Core Bug Triage Meeting Minutes Archive]]
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]]
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]]
* [[SDKBugTriageMinutesArchive|MeeGo SDK Bug Triage Meeting Minutes Archive]]

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo!

== Other references ==
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]

[[Category:QA]]

File:Bug triage 2.PNG

2011-07-14T01:56:48Z

Fan:

File:Bug triage.PNG

2011-07-14T01:55:56Z

Fan: uploaded a new version of "File:Bug triage.PNG"

File:Bug triage.PNG

2011-07-14T01:54:58Z

Fan: uploaded a new version of "File:Bug triage.PNG"

2011-07-13T09:19:30Z

Fan:

{{#bugzilla:
|columns=id,priority,status,assignee,summary
|to=need-triage@meego.com
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
}}