MeeGo wiki - User contributions [en]

Quality/Bugtriage

2011-07-13T04:30:51Z

Jerry: /* MeeGo Bug Triage Team */

== 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.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/jylha Petri Jylha], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo Tablet UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang]
|-
| 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/Bugtriage

2011-07-13T04:29:10Z

Jerry: /* MeeGo Bug Triage Team */

== 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.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/jylha Petri Jylha], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo Tablet UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang]
|-
| 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/Defects

2011-07-12T07:29:24Z

Jerry: /* Need System Debug */

=== Need System Debug ===
{{#bugzilla:
|columns=id,status,summary,to
|product=!security
|version=1.2
|status=!(CLOSED,VERIFIED,RELEASED,RESOLVED)
|keywords=need-sysdebug
|sort=id
|order=desc
|nameformat=login
}}
=== Need Owner ===
{{#bugzilla:
|columns=id,status,summary,to
|to=jerry.yu@intel.com
|version=1.2
|status=!(CLOSED,VERIFIED,RELEASED,RESOLVED)
|sort=id
|order=desc
|nameformat=login
}}

Quality/Defects

2011-07-12T07:28:57Z

Jerry: /* Need System Debug */

=== Need System Debug ===
{{#bugzilla:
|columns=id,status,summary,to
|product=!security
|version=1.2
|status=!(CLOSED,VERIFIED,RELEASED,RESOLVED)
|keywords=need-sysdebug
|sort=id
|order=desc
|nameformat=login
}}
=== Need System Debug ===
{{#bugzilla:
|columns=id,status,summary,to
|to=jerry.yu@intel.com
|version=1.2
|status=!(CLOSED,VERIFIED,RELEASED,RESOLVED)
|sort=id
|order=desc
|nameformat=login
}}

Quality/Defects

2011-07-12T07:27:12Z

Jerry: /* Need System Debug */

Quality/Defects

2011-07-12T05:13:22Z

Jerry: Created page with "=== Need System Debug === {{#bugzilla: |columns=id,status,summary,to |version=1.2 |status=!(CLOSED,VERIFIED,RELEASED,RESOLVED) |keywords=need-sysdebug |sort=id |order..."

=== Need System Debug ===
{{#bugzilla:
|columns=id,status,summary,to
|version=1.2
|status=!(CLOSED,VERIFIED,RELEASED,RESOLVED)
|keywords=need-sysdebug
|sort=id
|order=desc
|nameformat=login
}}

Quality

2011-07-05T02:50:07Z

Jerry: /* Projects */

= 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]] -- UPDATING IN PROGRESS, please contribute
* [[/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)
* [[/How_To_Report_Bugs|How to report bugs]]
* [[/Bug_Access_Restrictions|Bug Report Access Restrictions]]
* [[MeeGoBugzilla_Customization|Bugzilla customized features]]
* [[/MeeGoBugzillaRequestProcess|Requests for 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/TestSetGuideline

2011-06-27T07:40:20Z

Jerry: /* Test Set Definition */

== Purpose ==
The test set guideline could be referred to identify test cases which will be run in different MeeGo test cycle (hourly, daily, weekly, milestone release).

== Test Set vs. Test Cycle & Repo ==
[[File:testset-1.jpg]]

== Test Set Definition ==
* Sanity Test Set
** Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in sanity test reflects the most important and basic functionality of the distribution.
** Sanity test set is relatively stable and will be run on daily basis. [[../daily build test|More...]]

* Feature Testing
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.

* Dataflow
** Dataflow is the flow of data to, from and within a device. Inputs are derived from system use cases and each core dataflow test case presents the basic instance of the use case in MeeGo Core stack. The result of Core dataflow could report the maturity level of MeeGo Core OS software and hardware integration on specific device. It’s a weekly testing cycle against weekly build. [[../dataflow|More...]]

* Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.

* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.

* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

* Regression Test Set
** Regression test set is conducted to find out what works previously still work in this week release. Regression test set will be selected from MeeGo test suite based on changes in the image between last week and this week.
** Regression test set should run once a week against weekly pre-release image.

Steps to define regression test set:
# Figure out packages/features which have been changed between the image from last week and this week
# Identify all the related test cases for those affected packages and features. All the auto core test cases could be included in the regression test set since the execution cost is low. (need implement the mechanism in testlink).
# Auto regression test cases will be run in OTS. Long term goal is to run all the Core auto tests on all the MeeGo devices (Handset, Netbook etc...) automatically in OTS frequently.
# Manual tests will be run manually on target device

* Milestone Test Set
** To ensure MeeGo milestone (DP, FC, RC and PR)release with acceptance criteria, we would identify test set which should be run before milestone release. The objective is to report out more bugs and close outstanding bugs in each milestone release. The milestone test set will be selected from the above test sets to ensure MeeGo milestone release goal will be achieved. Details TBD.

Quality/TestSetGuideline

2011-06-15T01:07:02Z

Jerry: /* Test Set Definition */

== Purpose ==
The test set guideline could be referred to identify test cases which will be run in different MeeGo test cycle (hourly, daily, weekly, milestone release).

== Test Set vs. Test Cycle & Repo ==
[[File:testset-1.jpg]]

== Test Set Definition ==
* Sanity Test Set
** Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in sanity test reflects the most important and basic functionalities of the distribution.
** Sanity test set is relatively stable and will be run on daily basis.

* Feature Testing
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.

* Dataflow
** Dataflow is the flow of data to, from and within a device. Inputs are derived from system use cases and each core dataflow test case presents the basic instance of the use case in MeeGo Core stack. The result of Core dataflow could report the maturity level of MeeGo Core OS software and hardware integration on specific device. It’s a weekly testing cycle against weekly build. [[../dataflow|More...]]

* Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.

* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.

* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

* Regression Test Set
** Regression test set is conducted to find out what works previously still work in this week release. Regression test set will be selected from MeeGo test suite based on changes in the image between last week and this week.
** Regression test set should run once a week against weekly pre-release image.

Steps to define regression test set:
# Figure out packages/features which have been changed between the image from last week and this week
# Identify all the related test cases for those affected packages and features. All the auto core test cases could be included in the regression test set since the execution cost is low. (need implement the mechanism in testlink).
# Auto regression test cases will be run in OTS. Long term goal is to run all the Core auto tests on all the MeeGo devices (Handset, Netbook etc...) automatically in OTS frequently.
# Manual tests will be run manually on target device

* Milestone Test Set
** To ensure MeeGo milestone (DP, FC, RC and PR)release with acceptance criteria, we would identify test set which should be run before milestone release. The objective is to report out more bugs and close outstanding bugs in each milestone release. The milestone test set will be selected from the above test sets to ensure MeeGo milestone release goal will be achieved. Details TBD.

Quality/TestSetGuideline

2011-06-15T01:02:13Z

Jerry: /* Test Set Definition */

== Purpose ==
The test set guideline could be referred to identify test cases which will be run in different MeeGo test cycle (hourly, daily, weekly, milestone release).

== Test Set vs. Test Cycle & Repo ==
[[File:testset-1.jpg]]

== Test Set Definition ==
* Sanity Test Set
** Sanity test set is a very brief run-through of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in sanity test reflects the most important and basic functionalities of the distribution.
** Sanity test set is relatively stable and will be run on daily basis.

* Feature Testing
** Key Feature Test Set is used to verify MeeGo Handset UX most critical key use cases functionalities with well selected basic feature test cases.
** Basic Feature Test Set is verifying MeeGo HandSet UX delivered features with basic feature test cases. Test set is always static to show overall feature functionalities progress and maturity of the entire MeeGo distribution. Based on test results QA is able to identify components with working features to enable extended feature testing and system testing.

* Dataflow
** Dataflow is the flow of data to, from and within a device. Inputs are derived from system use cases and each core dataflow test case presents the basic instance of the use case in MeeGo Core stack. The result of Core dataflow could report the maturity level of MeeGo Core OS software and hardware integration on specific device. It’s a weekly testing cycle against weekly build. [[../dataflow|More...]]

** Extended Feature Test Set is used to verify delivery of features forming full functionality of entirely component. After component is fully integrated all component related test cases will be executed for selected weekly release and report out all the bugs against component and it’s features. Extended feature test set will be run again in the upcoming milestone or when significant changes are applied to component and it’s features.

* System Functional
** System Functional Test Set is targeting to evaluate delivered functionalities from system perspective. Test cases are not testing UI or Application itself, instead test cases are testing how whole system is working and interacting with Consumer (end user). Test cases are covering most critical interaction and negative scenarios that consumers will encounter in their daily usage.

* System Non-Functional
** System Performance Test Sets target is to evaluate overall system performance by executing well-selected set of cases from different test areas - for example response and reaction times, use times and frame rate measurements. Test set gives a quick view of system performance from end-user point of view.
** System Reliability Test Sets target is to provide an overview to system reliability by executing iterative tests that focus on the most important and most used end-user features of MeeGo.

* Regression Test Set
** Regression test set is conducted to find out what works previously still work in this week release. Regression test set will be selected from MeeGo test suite based on changes in the image between last week and this week.
** Regression test set should run once a week against weekly pre-release image.

Steps to define regression test set:
# Figure out packages/features which have been changed between the image from last week and this week
# Identify all the related test cases for those affected packages and features. All the auto core test cases could be included in the regression test set since the execution cost is low. (need implement the mechanism in testlink).
# Auto regression test cases will be run in OTS. Long term goal is to run all the Core auto tests on all the MeeGo devices (Handset, Netbook etc...) automatically in OTS frequently.
# Manual tests will be run manually on target device

* Milestone Test Set
** To ensure MeeGo milestone (DP, FC, RC and PR)release with acceptance criteria, we would identify test set which should be run before milestone release. The objective is to report out more bugs and close outstanding bugs in each milestone release. The milestone test set will be selected from the above test sets to ensure MeeGo milestone release goal will be achieved. Details TBD.

Quality/TestSuite/MCTS

2011-05-24T04:59:56Z

Jerry: /* Known Issues */

Quality/meego core feature/1.3

2011-05-22T13:56:01Z

Jerry: /* Planed Features for MeeGo Core 1.3 */

== Planned Features for MeeGo Core 1.3 ==
=== Working in progress ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=ACCEPTED,REOPENED
|sort=id
|order=desc
|nameformat=login
}}
=== Resolved ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RESOLVED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|lastcomment=1
|noresultsmessage=There is no resolved feature pending for integration
}}

=== Released ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RELEASED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=No feature in "RELEASED" status
}}
=== Verified ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=VERIFIED,CLOSED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
}}

== Requirements Requested but not Accepted yet ==
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=NEW,INDEFINITION
|sort=id
|order=desc
|nameformat=login
}}

Quality/meego core feature/1.3

2011-05-22T13:38:34Z

Jerry: /* Verified */

== Planed Features for MeeGo Core 1.3 ==
=== Working in progress ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=ACCEPTED,REOPENED
|sort=id
|order=desc
|nameformat=login
}}
=== Resolved ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RESOLVED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|lastcomment=1
|noresultsmessage=There is no resolved feature pending for integration
}}

=== Released ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RELEASED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=No feature in "RELEASED" status
}}
=== Verified ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=VERIFIED,CLOSED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
}}

== Requirements Requested but not Accepted yet ==
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=NEW,INDEFINITION
|sort=id
|order=desc
|nameformat=login
}}

Quality/meego core feature/1.3

2011-05-22T13:37:15Z

Jerry: /* Verified */

== Planed Features for MeeGo Core 1.3 ==
=== Working in progress ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=ACCEPTED,REOPENED
|sort=id
|order=desc
|nameformat=login
}}
=== Resolved ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RESOLVED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|lastcomment=1
|noresultsmessage=There is no resolved feature pending for integration
}}

=== Released ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RELEASED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=No feature in "RELEASED" status
}}
=== Verified ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=VERIFIED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
}}
== Requirements Requested but not Accepted yet ==
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=NEW,INDEFINITION
|sort=id
|order=desc
|nameformat=login
}}

Quality/meego core feature/1.3

2011-05-22T13:29:50Z

Jerry: /* Resolved */

== Planed Features for MeeGo Core 1.3 ==
=== Working in progress ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=ACCEPTED,REOPENED
|sort=id
|order=desc
|nameformat=login
}}
=== Resolved ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RESOLVED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|lastcomment=1
|noresultsmessage=There is no resolved feature pending for integration
}}

=== Released ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RELEASED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=No feature in "RELEASED" status
}}
=== Verified ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=VERIFIED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
}}

Quality/meego core feature/1.3

2011-05-22T13:26:54Z

Jerry: /* 1.3 Planed Features */

== Planed Features for MeeGo Core 1.3 ==
=== Working in progress ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=ACCEPTED,REOPENED
|sort=id
|order=desc
|nameformat=login
}}
=== Resolved ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RESOLVED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=There is no resolved feature pending for integration
}}
=== Released ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RELEASED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=No feature in "RELEASED" status
}}
=== Verified ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=VERIFIED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
}}

Quality/meego core feature/1.3

2011-05-22T13:25:25Z

Jerry: Created page with "== 1.3 Planed Features == === Working in progress === {{#bugzilla: |columns=id,status,summary,to |product=MeeGo Core OS Features |version=1.3 |status=ACCEPTED,REOPENED ..."

== 1.3 Planed Features ==
=== Working in progress ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=ACCEPTED,REOPENED
|sort=id
|order=desc
|nameformat=login
}}
=== Resolved ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RESOLVED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=There is no resolved feature pending for integration
}}
=== Released ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=RELEASED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
|noresultsmessage=No feature in "RELEASED" status
}}
=== Verified ===
{{#bugzilla:
|columns=id,status,summary,to
|product=MeeGo Core OS Features
|version=1.3
|status=VERIFIED
|sort=id
|order=desc
|nameformat=login
|resolution=!(REJECTED,DUPLICATE)
}}

Quality/TestSuite/MCTS

2011-05-17T07:34:54Z

Jerry: /* Test Suite Code & API Coverage Analysis Repositories */

Quality/TestSuite/MCTS/MCTS Start Contributing

2011-05-17T07:24:16Z

Jerry: /* Overview of Contributions */

== Overview of Contributions ==

The MCTS consists of test packages for various areas. If you are interested in developing
test cases to an existing test package, you should first contact the maintainer of the test
package. The maintainer for a test package is responsible for incorporating the test cases
to the package and ensure that your test cases meet the quality criteria. The maintainer instructs
you how, in practice, your test cases are brought to the clone of the MCTS she/he manages.
At the end, the maintainer will submit the merge request containing your test cases to the MCTS
maintainer who creates the MCTS release. The current maintainers are indicated in the content
description tables in [[Quality/TestSuite/MCTS|MCTS main page]].

If you are interested in creating a whole new test package, you should directly contact
MCTS maintainer [mailto:jeff.zheng@intel.com Jeff Zheng] to request your package is to be included to MCTS release.
With such a request, you need to nominate a maintainer for the test package,
who is responsible to ensure that the quality criteria is met. The maintainer needs to
create a clone of the MCTS master repository where changes are to be committed and
create merge requests towards MCTS release. In addition, the nominated maintainer
must create a process where test cases can be incorporated to the package
from other developers. The merge requests and release process is described in
[[Quality/TestSuite/MCTS/MCTS_Release_Process|MCTS Release Process]] page and
the existing releases and future plans is described in [[Quality/TestSuite/MCTS/MCTS_Releases|MCTS Releases]] page.

Quality/Meetings

2011-05-06T02:21:59Z

Jerry: /* Next Meeting */

== Logistics ==

Until further notice, the MeeGo QA meets every Tuesday at 07:00 UTC for one hour.
All MeeGo QA meetings take place in the MeeGo IRC channels:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-qa
Propose a topic in advance by editing this page (#Next Meeting). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18h before the meeting. If there is too many items then V-PV will pick the topics to be discussed.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==
'''Tuesday May 10th 2011 07:00 UTC''' - Agenda Proposal

This meeting is focusing different process and procedure related items. If time we will also have short period for questions to QA Leads. Please anyhow remember to update your verticals QA status.

* Opening and general news
* Actions from previous meetings (2011-05-03)
* Discussion/approach for usage of test packages from components
* Unify "test type" name on qa-reports.meego.com
* Update to 1.2 QA Situation (QA Leads and QA-tools)
** Leads create short summary to Wiki min 1h prior the meeting so that in the meeting we can concentrate on questions and discussion
** [[Quality/Meetings/QA leads update 1.2| Weekly Updates from QA Leads]]

== Logs ==
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-03-07.00.html 2011-05-03 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-04-26-06.59.html 2011-04-26 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-19-07.00.html 2011-04-19 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-07.01.html 2011-04-12 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-29-07.06.html 2011-03-29 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-22-07.08.html 2011-03-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-15-06.59.html 2011-03-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-01-06.59.html 2011-03-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-22-07.00.html 2011-02-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-15-07.00.html 2011-02-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-08-07.00.html 2011-02-08 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-01-06.59.html 2011-02-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-25-07.01.html 2011-01-25 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-06.59.html 2011-01-18 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-06.59.html 2011-01-11 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-04-07.00.html 2011-01-04 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-28-07.00.html 2010-12-28 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-21-07.02.html 2010-12-21 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-14-07.01.html 2010-12-14 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-06.59.html 2010-12-07 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-06.59.html 2010-11-30 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-06.59.html 2010-11-23 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-14.31.html 2010-11-09 Meeting minutes]

== Materials used in meetings - if not anyplace else ==
* [[Quality/Meetings/QA nominations 101201| QA Nomination proposals for 1st of Dec 2010 TSG Meeting]]
* [[File:QAtoolproposal.pdf]] - proposal about new QA tool discussed on Dublin QA Workshop (un-conference day)

Quality/Meetings

2011-05-06T02:21:29Z

Jerry: /* Next Meeting */

== Logistics ==

Until further notice, the MeeGo QA meets every Tuesday at 07:00 UTC for one hour.
All MeeGo QA meetings take place in the MeeGo IRC channels:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-qa
Propose a topic in advance by editing this page (#Next Meeting). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18h before the meeting. If there is too many items then V-PV will pick the topics to be discussed.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==
'''Tuesday May 10th 2011 07:00 UTC''' - Agenda Proposal

This meeting is focusing different process and procedure related items. If time we will also have short period for questions to QA Leads. Please anyhow remember to update your verticals QA status.

* Opening and general news
* Actions from previous meetings (2011-05-03)
* Discussion/approach for usage of test packages from components
* unified "test type" name on qa-reports.meego.com
* Update to 1.2 QA Situation (QA Leads and QA-tools)
** Leads create short summary to Wiki min 1h prior the meeting so that in the meeting we can concentrate on questions and discussion
** [[Quality/Meetings/QA leads update 1.2| Weekly Updates from QA Leads]]

== Logs ==
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-05-03-07.00.html 2011-05-03 Meeting Minutes]
* [http://irclogs.meego.com/meetbot/meego-meeting/2011/meego-meeting.2011-04-26-06.59.html 2011-04-26 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-19-07.00.html 2011-04-19 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-07.01.html 2011-04-12 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-29-07.06.html 2011-03-29 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-22-07.08.html 2011-03-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-15-06.59.html 2011-03-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-01-06.59.html 2011-03-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-22-07.00.html 2011-02-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-15-07.00.html 2011-02-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-08-07.00.html 2011-02-08 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-01-06.59.html 2011-02-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-25-07.01.html 2011-01-25 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-06.59.html 2011-01-18 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-06.59.html 2011-01-11 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-04-07.00.html 2011-01-04 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-28-07.00.html 2010-12-28 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-21-07.02.html 2010-12-21 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-14-07.01.html 2010-12-14 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-06.59.html 2010-12-07 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-06.59.html 2010-11-30 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-06.59.html 2010-11-23 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-14.31.html 2010-11-09 Meeting minutes]

== Materials used in meetings - if not anyplace else ==
* [[Quality/Meetings/QA nominations 101201| QA Nomination proposals for 1st of Dec 2010 TSG Meeting]]
* [[File:QAtoolproposal.pdf]] - proposal about new QA tool discussed on Dublin QA Workshop (un-conference day)

Quality/TestSuite/MCTS

2011-05-04T06:52:21Z

Jerry: /* Known Issues */

Quality/TestSuite/MCTS

2011-05-04T06:51:09Z

Jerry: /* Known Issues */

Quality/TestSuite/MCTS

2011-05-03T02:35:18Z

Jerry: /* MCTS Releases */

Quality/Meetings

2011-04-18T12:19:23Z

Jerry: /* Next Meeting */

== Logistics ==

Until further notice, the MeeGo QA meets every Tuesday at 07:00 UTC for one hour.
All MeeGo QA meetings take place in the MeeGo IRC channels:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-qa
Propose a topic in advance by editing this page (#Next Meeting). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18h before the meeting. If there is too many items then V-PV will pick the topics to be discussed.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==
'''Tuesday April 19th 2011 07:00 UTC''' - Agenda Proposal

This time we will be focusing different process and procedure related items. If time we will also have short period for questions to QA Leads. Please anyhow remember to update your verticals QA status.

* Opening and general news
* Actions from previous meetings (2011-04-12)
* Closing agreements for Test Types
** See test type definitions on http://wiki.meego.com/Quality/Test_areas_and_types
* Update to 1.2 QA Situation (QA Leads)
** Leads create short summary to Wiki min 1h prior the meeting so that in the meeting we can concentrate on questions and discussion
** [[Quality/Meetings/QA leads update 1.2| Weekly Updates from QA Leads]]
* MeeGo 1.2 release QA Plan sharing(Jerry)
* QA-Tools update
** QA tools lead. Current lead Ville Ilvonen has moved to other projects and we need to make a new nomination proposal to TSG.

== Logs ==
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-04-12-07.01.html 2011-04-12 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-29-07.06.html 2011-03-29 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-22-07.08.html 2011-03-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-15-06.59.html 2011-03-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-03-01-06.59.html 2011-03-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-22-07.00.html 2011-02-22 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-15-07.00.html 2011-02-15 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-08-07.00.html 2011-02-08 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-02-01-06.59.html 2011-02-01 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-25-07.01.html 2011-01-25 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-18-06.59.html 2011-01-18 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-11-06.59.html 2011-01-11 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-04-07.00.html 2011-01-04 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-28-07.00.html 2010-12-28 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-21-07.02.html 2010-12-21 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-14-07.01.html 2010-12-14 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-12-07-06.59.html 2010-12-07 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-30-06.59.html 2010-11-30 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-23-06.59.html 2010-11-23 Meeting Minutes]
* [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-09-14.31.html 2010-11-09 Meeting minutes]

== Materials used in meetings - if not anyplace else ==
* [[Quality/Meetings/QA nominations 101201| QA Nomination proposals for 1st of Dec 2010 TSG Meeting]]
* [[File:QAtoolproposal.pdf]] - proposal about new QA tool discussed on Dublin QA Workshop (un-conference day)

Quality/TestSuite/MCTS

2011-04-18T11:36:47Z

Jerry: /* MeeGo Core Test Suite (MCTS) */

Quality/TestSuite/MCTS

2011-04-02T02:33:06Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [[Quality/Plans/MeeGo_Core_Test_Plan|Test Coverage]]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "2" | Security

| Accounts || || || mcts-mwts-accounts|| [mailto:pauli-pekka.toivanen@digia.com Pauli-Pekka Toivanen] ||

|-
| Single Sign-On || || || mcts-mwts-accounts|| [mailto:pauli-pekka.toivanen@digia.com Pauli-Pekka Toivanen] ||

|-
| rowspan = "4" | System

| System Control || || || mcts-mwts-feedback || [mailto:jan.grela@digia.com Jan Grela] ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:liang.jin@intel.com Liang Jin] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || mcts-mwts-pim || [mailto:arto.katajasalo@digia.com Arto Katajasalo] ||

|-
| Contacts Engine || Average || || mcts-mwts-pim || [mailto:arto.katajasalo@digia.com Arto Katajasalo] ||

|-
| Email Engine || Average || || WIP || [mailto:yongbo.wu@elektrobit.com Yongbo Wu] ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || mcts-mwts-buteo || [mailto:pauli-pekka.toivanen@digia.com Pauli-Pekka Toivanen] ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:zhiqiang.zhang@intel.com Zhiqiang Zhang] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:zhiqiang.zhang@intel.com Zhiqiang Zhang] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || [mailto:arttu.valo@digia.com Arttu Valo] ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||15% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || [mailto:pauli-pekka.toivanen@digia.com Pauli-Pekka Toivanen] ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || mcts-mwts-pim|| [mailto:arto.katajasalo@digia.com Arto Katajasalo] ||

|-
| QtM Location || || || mcts-mwts-location || [mailto:tuomo.pelkonen@digia.com Tuomo Pelkonen] ||

|-
| QtM Messaging || || || mcts-mwts-messaging || [mailto:arttu.valo@digia.com Arttu Valo] ||

|-
| QtM Publish & Subscribe || || || WIP || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || [mailto:reijo.korhonen@digia.com Reijo Korhonen] ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || mcts-mwts-pim|| [mailto:arto.katajasalo@digia.com Arto Katajasalo] ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || [mailto:jan.grela@digia.com Jan Grela] ||

|-
| QtM System Info || || || mcts-mwts-systeminfo|| [mailto:reijo.korhonen@digia.com Reijo Korhonen] ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===

For test suite description, click the component name

{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:jussi.saavalainen@digia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:jussi.saavalainen@digia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:jussi.saavalainen@digia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:jussi.saavalainen@digia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T14:24:11Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || mcts-mwts-accounts|| ||

|-
| Single Sign-On || || || mcts-mwts-accounts|| ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || mcts-mwts-pim|| ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || WIP || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || mcts-mwts-pim|| ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || mcts-mwts-systeminfo|| ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T14:23:00Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || WIP || ||

|-
| Single Sign-On || || || WIP || ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || mcts-mwts-pim|| ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || WIP || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || mcts-mwts-pim|| ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || mcts-mwts-systeminfo|| ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T14:20:20Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || WIP || ||

|-
| Single Sign-On || || || WIP || ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || mcts-mwts-pim|| ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || WIP || || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || WIP || || ||

|-
| QtM Versit || || || mcts-mwts-pim|| ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || mcts-mwts-systeminfo|| ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T13:23:55Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || WIP || ||

|-
| Single Sign-On || || || WIP || ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || mcts-mwts-pim|| ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || WIP || || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || mcts-mwts-pim|| ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || mcts-mwts-systeminfo|| ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T13:18:52Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || WIP || ||

|-
| Single Sign-On || || || WIP || ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || WIP || ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || WIP || || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || WIP || ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T13:09:07Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || WIP || ||

|-
| Single Sign-On || || || WIP || ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || WIP || ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || WIP || || ||

|-
| QtM Sensors || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || WIP || ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || [mailto:jingke.zhang@intel.com Jingke Zhang] ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2011-01-23T13:04:51Z

Jerry: /* MCTS Test Packages Mapping to MeeGo 1.2 Architecture */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || WIP || ||

|-
| Single Sign-On || || || WIP || ||

|-
| Integrity Protection Framework || || || WIP || ||

|-
| Certificate Manager || || || WIP || ||

|-
| SW Distribution Security || || || WIP || ||

|-
| Access Control Framework || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || WIP || ||

|-
| Resource Policy ||light || || || ||

|-
| Context Framework || Through || || WIP || ||

|-
| Sensor Framework || Average || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || WIP || ||

|-
| Contacts Engine || Average || || WIP || ||

|-
| Email Engine || Average || || WIP || ||

|-
| Backup Framework || Average || || WIP || ||

|-
| Synchronization Framework || Average || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||
|-
| UPnP || light ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || N/A || ||

|-
| Qt Web Runtime || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || WIP || ||

|-
| QtM Location || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || WIP || || ||

|-
| QtM Sensors || || mcts-mwts-sensors || || ||

|-
| QtM Service Framework || || || WIP || ||

|-
| QtM Versit || || || WIP || ||

|-
| QtM Multimedia || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf mcts-openvg-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Font Management || || || N/A || ||

|-
| X11 || Light ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev mcts-display-tests || [mailto:wei.z.zhang@intel.com Wei Z Zhang] ||

|-
| Data Management || Content Framework || Through || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem mcts-system-tests || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/Meetings/QA leads update 1.2

2011-01-11T08:08:56Z

Jerry: /* IVI Update */

=== Core Update ===
11.01.2011

- Quite a few features are released yet.
- Acceptance and Sanity set automation proceeding, all but seven cases currently automated. Test run cycle will be increased, goal to be run once in a hour.
- Common verdict rules for test cases agreed. Only three verdicts will be given by QA, Pass, Fail and N/A. Measured and blocked verdicts are not supported. http://wiki.meego.com/Quality/Glossary#Test_case_verdict

Link to latest testing results:
http://qa-reports.meego.com/1.2/Core/Dataflow/N900/600
Run rate 68% +23%
Pass rate of total 48% +13%
Pass rate of executed 71% -7%

=== Handheld Update ===
11.01.2011
* Currently focusing to Acceptance, Sanity and Key Feature Testing
* Test results for Handset: http://qa-reports.meego.com/1.2/Handset/
* Latest N900 Key Feature Results: http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature/N900
** Run Rate / Pass Rate: 97% / 67%, both increased bit compared to previous week
* Latest nCDK Key Feature Results: http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature/Ncdk
** Run Rate / Pass Rate: 95% / 60%, both increased compared to previous week
* Initial NFR's got from Product Management. Study ongoing.
* Ramp-Up followed: http://wiki.meego.com/Quality/Plans/Handset_UX_ramp-up_1.2

=== Netbook Update ===
* MeeGo 1.0 SW Update: QA completed 1 round of fullpass testing and regression testing for 1.0 SW update release 6, system functional pass ratio is improved to 93.30% compared with 92.93% in update release 5 and no regression issue found; 1.0 SW update release 6 will be released in 11st Jan, 2011; 1.0 SW update release 7 will code freeze in 18th Feb, 2011 and release in 25th Feb, 2011;

* MeeGo 1.1 SW Update: QA complete 1 round of fullpass testing and regression testing for 1.1 SW update release 2, system functional pass ratio is improved to 90.40% compared with 90.04% in update release 1. No major regression issue found by QA; 1.1 SW update release 2 will be released in 11st Jan, 2011;

* MeeGo 1.2: QA completed 3 rounds of daily testing on Netbook 1.2 image to cover Netbook UX and Core components; 1.2 trunk: Netbook UX sanity pass ratio is 75%, which keep stable; For core parts, sanity pass ratio is 100%;

=== IVI Update ===
11.01.2011
* Most driver for Russellville are dropped while switching to new kernel adaptation. 10 regression bugs about driver missing are filed, including SPI(11964), Xiic I2C(11965), iNAND(11966), timb SD slot(11967), timb radio(11968), BT/UART(11912), touch screen(11955), etc
* Ethernet driver for Russellville is integrated into new kernel adaptation for Intel automotive, fixed bug 9240. However, it causes system easily hang up with onboard Ethernet connected(11979).

=== SDK Update ===
dd.mm.yyyy
New things has happened

Quality/Meetings/QA leads update 1.2

2011-01-11T07:21:54Z

Jerry: /* Core Update */

=== Core Update ===
11.01.2011

- Quite a few features are released yet.
- Acceptance and Sanity set automation proceeding, all but seven cases currently automated. Test run cycle will be increased, goal to be run once in a hour.
- Common verdict rules for test cases agreed. Only three verdicts will be given by QA, Pass, Fail and N/A. Measured and blocked verdicts are not supported. http://wiki.meego.com/Quality/Glossary#Test_case_verdict

Link to latest testing results:
http://qa-reports.meego.com/1.2/Core/Dataflow/N900/600
Run rate 68% +23%
Pass rate of total 48% +13%
Pass rate of executed 71% -7%

=== Handheld Update ===
11.01.2011
* Currently focusing to Acceptance, Sanity and Key Feature Testing
* Test results for Handset: http://qa-reports.meego.com/1.2/Handset/
* Latest N900 Key Feature Results: http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature/N900
** Run Rate / Pass Rate: 97% / 67%, both increased bit compared to previous week
* Latest nCDK Key Feature Results: http://qa-reports.meego.com/1.2/Handset/Key%20Basic%20Feature/Ncdk
** Run Rate / Pass Rate: 95% / 60%, both increased compared to previous week
* Initial NFR's got from Product Management. Study ongoing.
* Ramp-Up followed: http://wiki.meego.com/Quality/Plans/Handset_UX_ramp-up_1.2

=== Netbook Update ===
* MeeGo 1.0 SW Update: QA completed 1 round of fullpass testing and regression testing for 1.0 SW update release 6, system functional pass ratio is improved to 93.30% compared with 92.93% in update release 5 and no regression issue found; 1.0 SW update release 6 will be released in 11st Jan, 2011; 1.0 SW update release 7 will code freeze in 18th Feb, 2011 and release in 25th Feb, 2011;

* MeeGo 1.1 SW Update: QA complete 1 round of fullpass testing and regression testing for 1.1 SW update release 2, system functional pass ratio is improved to 90.40% compared with 90.04% in update release 1. No major regression issue found by QA; 1.1 SW update release 3 will be released in 11st Jan, 2011;

* MeeGo 1.2: QA completed 3 rounds of daily testing on Netbook 1.2 image to cover Netbook UX and Core components; 1.2 trunk: Netbook UX sanity pass ratio is 75%, which keep stable; For core parts, sanity pass ratio is 100%;

=== IVI Update ===
dd.mm.yyyy
New things has happened

=== SDK Update ===
dd.mm.yyyy
New things has happened

Quality/TestSuite/MCTS

2011-01-04T07:21:03Z

Jerry: /* Test Suite Status For Middleware (New) */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===

* MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 
* Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design
* Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://meego.gitorious.org/meego-quality-assurance/mcts 
You can get the coverage analysis documents here: http://meego.gitorious.org/meego-quality-assurance/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== MCTS Test Packages Mapping to MeeGo 1.2 Architecture ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| [[../GeoClue Test Plan | Location Framework]] || light ||100% ||100% || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| [[../PulseAudio Test Plan | PulseAudio ]]|| light ||100% ||100% || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] || Dec. 17 for test plan

|-
| UPnP || light ||100% ||0% || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| [[/OFono Test Plan |Cellular Framework]] || Through ||100% ||36% || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through ||100% ||43% || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| [[/MeeGo Bluez Test Plan |Bluetooth]] || Average ||100% ||16% || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | [[../MeeGo_Graphics_Test_Plan | Graphics]]
| OpenGL ES || Average ||100% ||13% || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light ||100% ||100% || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| [[ Package_Manager | Package Management and Update]] || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] || .

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Developed But Not Released Middleware Test Asset Descriptions ===
[[../MWTS Not Released Asset Descriptions | Developed Not Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "17" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../Framebuffer Test Specification | Framebuffer Driver]] || '''Light''' || 22 || 11 || 0% || [mailto:mika.niinisto@digia.com Mika Niinistö] ||tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../Input Devices Driver Test Specification | Input Devices Driver]] || '''Light''' || 3 || 3 || 0% || ||tbd

|-
| [[../oFono Modem API Test Specification | Modem Driver]] || '''Light''' || N/A || N/A || N/A || ||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Test Front-end | Sensor Driver]] || '''N/A''' || N/A || N/A || N/A || Pasi Matilainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Average''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../Watchdog Driver Test Specification | Watchdog Driver]] || '''Average''' || 3 || 3 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../X11 Test Specification | X11]] || '''Light''' || 11 || 11 || 0% || [mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd
|}

Quality/TestSuite/MCTS

2010-12-08T06:09:29Z

Jerry: /* Test Suite Readme */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===
INTRODUCTION 
SOURCE CODE AND COMPILING 
TEST ENVIRONMENT 
EXECUTING TESTS 
TEST RESULTS 
KNOWN ISSUES 

MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 

Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design

Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| Location Framework || light || || || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light || || || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||

|-
| UPnP || light || || || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| Cellular Framework || Through || || || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through || || || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| Bluetooth || Average || || || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | Graphics
| OpenGL ES || Average || || || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light || || || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] ||

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Test Suite Status For Middleware (Obsolete) ===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Bugzilla component
!|[[Quality/Plans/MeeGo_Core_Test_Plan#Test_Coverage_Definition |Test Coverage]]
!|Planned #
!|Ready #
!|In Git #
!|Auto %
!|Test Asset Maintainer
!|QA CCed
!|Availability in GIT

|-
| rowspan = "5" | Comms Services || [[../oFono Test Plan | Telephony (oFono)]] || Telephony || '''Thorough''' ||~1000||112||112||29%|| [mailto:elva.fu@intel.com Elva Fu] || ||tbd

|-
| [[../oFono Modem API Test Specification | Telephony (oFono Modem API)]] || Modem Support || '''Thorough''' ||36||36||36||tbd|| [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]|| [mailto:elva.fu@intel.com Elva Fu] || http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-ofono

|-
| [[../ConnMan Test Plan | Connection Management (ConnMan)]] || Connection Manager || '''Thorough''' ||392||392||392||44%|| [mailto:jeff.zheng@intel.com Jeff Zheng] ||||Aug.30 2010

|-
| [[../Bluetooth Test Plan | Bluetooth (BlueZ)]] || Bluetooth || '''Average''' ||60||60||60||16%|| [mailto:jingke.zhang@intel.com Jingke] || ||Aug.30 2010

|-
| [[../Telepathy Test Plan | VOIP, IM and Pres (Telepathy)]] || VoIP and IM || '''Light''' || 22 || 8 || || 0 || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] ||[mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:xiaolei.zhang@intel.com Xiaolei Zhang] || Sep.10.2010

|-
| rowspan = "4" | Internet Services || Layout Engine (WebKit) || Internet layout engine || Not Covered || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| Web RunTime (WebKit) || Web run time || Open || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| [[../Libsocialweb Test Plan | Web Services (libsocialweb)]] || Web Services || '''Thorough''' || 55 || 55 ||55 || 45% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Sept.20 2010

|-
| [[../GeoClue Test Plan | Location (GeoClue)]] || Location || '''Light''' ||30||26 ||26||100% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Aug.30 2010

|-
| rowspan = "6" | Visual Services || 3D Graphics (OpenGL/GLES) || Graphics Subsystem || '''Average''' ||1067||1067||1067||100% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| [[../OpenGLGLES Performance Test Specification | OpenGL/GLES Performance]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-opengles2-perf

|-
| 2D Graphics (QPainter) || Graphics Subsystem || Not Covered || || || || || ||[mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| GTK/Clutter|| Clutter || '''Light''' ||43||43 ||43 ||0% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| X (x/rendercheck) || || '''Light''' ||19||19||19||100% || [mailto:kui.zheng@intel.com Kui Zheng] || || Aug.30 2010

|-
| [[../X11 Test Specification | X11 ]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-x11

|-
| rowspan = "5" | Media Services || [[../GStreamer Test Plan | Media Framework (GStreamer)]] || Media Subsystem || '''Light''' || 260 || 260 |||| 100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan]|| Sep.10.2010

|-
| [[../Gstreamer_plugin Test Plan | Camera (Gstreamer plug-in)]] || Media Subsystem || '''Light''' || 17 || 17 ||||100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] || Sep.10.2010

|-
| Codecs (Gstreamer plug-in) || Media Subsystem || '''Light''' || Covered via Media Framework TC's || || || || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] ||

|-
| [[../PulseAudio Test Plan | Audio (PulseAudio)]] || PulseAudio || '''Light''' || 13 || 13 || 13 || 100% || [mailto:hao.h.chen@intel.com Hao Chen] || || Sep.10.2010

|-
| [[../UPnP Test Plan | GUPnP]] || Media Subsystem || '''Light''' || 25|| 25 || 25 || 0% || [mailto:daniel.tao@intel.com Daniel Tao] || ||Sept. 6 2010

|-
| rowspan = "3" | Data Management || [[../Tracker Test Plan | Content Framework (Tracker)]] || Content Framework || '''Thorough''' || 30 || 17 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang]||

|-
| [[../ContextKit Test Plan | Context Framework (ContextKit)]] || Context Framework (ContextKit) || '''Thorough''' || 15 || 5 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| Package Manager (PackageKit) || Package Manager || '''Light''' ||10 ||10 ||10 ||0% ||[mailto:huajun.li@intel.com Huajun Li] || ||Sept. 22, 2010

|-
| rowspan = "4" | Device Services || [[../Device Health Test Plan | Device Health (DSME)]] || || '''Thorough''' || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| [[../MWTS Asset Sensors Description | Sensor Framework]] || Sensor Framework || '''Average''' || 16 || 0 || ||0% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-mark.halmagiu@nokia.com Mark Halmagiu] [mailto:yi.fu@intel.com Yi Fu] || tbd
|-
| [[../Resource Manager Test Plan | Resource Manager (System Policy Manager)]] || || '''Average''' || 50 || 0 || ||tbd || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:xiaolei.zhang@intel.com Xialei Zhang]|| tbd
|-
| Backup & Restore || Backup & Restore || Open || || || |||| ||

|-
| rowspan = "3" | Personal Services || [[../PIM Test Plan | PIM services]] || PIM services || '''Average''' || 23 || 0 |||| tbd ||[mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| [[../Buteo Test Plan | Device Sync (Buteo)]] || Device Sync || '''Thorough''' || WIP || || |||| [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| Accts & SSO || || Open || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd
|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "12" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Avarage''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd
|}

Quality/TestSuite/MCTS

2010-12-08T06:08:46Z

Jerry: /* Test Suite Status For Middleware (New) */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===
INTRODUCTION 
SOURCE CODE AND COMPILING 
TEST ENVIRONMENT 
EXECUTING TESTS 
TEST RESULTS 
KNOWN ISSUES 

MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 

Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design

Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Readme ===

[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-ofono-tests/README oFono ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-connman-tests/README ConnMan ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-bluez-tests/README BlueZ ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-geoclue-tests/README GeoClue ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-piglit-tests/README 3D Graphics ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-clutter-tests/README Clutter ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-x-tests/README X ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-pulseaudio-tests/README PulseAudio ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-gupnp-tests/README GUPnP ]] 

[[/readme_template | Test Package README Template]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "4" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| Location Framework || light || || || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light || || || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||

|-
| UPnP || light || || || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| Cellular Framework || Through || || || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through || || || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| Bluetooth || Average || || || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | Graphics
| OpenGL ES || Average || || || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light || || || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] ||

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Test Suite Status For Middleware (Obsolete) ===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Bugzilla component
!|[[Quality/Plans/MeeGo_Core_Test_Plan#Test_Coverage_Definition |Test Coverage]]
!|Planned #
!|Ready #
!|In Git #
!|Auto %
!|Test Asset Maintainer
!|QA CCed
!|Availability in GIT

|-
| rowspan = "5" | Comms Services || [[../oFono Test Plan | Telephony (oFono)]] || Telephony || '''Thorough''' ||~1000||112||112||29%|| [mailto:elva.fu@intel.com Elva Fu] || ||tbd

|-
| [[../oFono Modem API Test Specification | Telephony (oFono Modem API)]] || Modem Support || '''Thorough''' ||36||36||36||tbd|| [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]|| [mailto:elva.fu@intel.com Elva Fu] || http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-ofono

|-
| [[../ConnMan Test Plan | Connection Management (ConnMan)]] || Connection Manager || '''Thorough''' ||392||392||392||44%|| [mailto:jeff.zheng@intel.com Jeff Zheng] ||||Aug.30 2010

|-
| [[../Bluetooth Test Plan | Bluetooth (BlueZ)]] || Bluetooth || '''Average''' ||60||60||60||16%|| [mailto:jingke.zhang@intel.com Jingke] || ||Aug.30 2010

|-
| [[../Telepathy Test Plan | VOIP, IM and Pres (Telepathy)]] || VoIP and IM || '''Light''' || 22 || 8 || || 0 || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] ||[mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:xiaolei.zhang@intel.com Xiaolei Zhang] || Sep.10.2010

|-
| rowspan = "4" | Internet Services || Layout Engine (WebKit) || Internet layout engine || Not Covered || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| Web RunTime (WebKit) || Web run time || Open || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| [[../Libsocialweb Test Plan | Web Services (libsocialweb)]] || Web Services || '''Thorough''' || 55 || 55 ||55 || 45% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Sept.20 2010

|-
| [[../GeoClue Test Plan | Location (GeoClue)]] || Location || '''Light''' ||30||26 ||26||100% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Aug.30 2010

|-
| rowspan = "6" | Visual Services || 3D Graphics (OpenGL/GLES) || Graphics Subsystem || '''Average''' ||1067||1067||1067||100% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| [[../OpenGLGLES Performance Test Specification | OpenGL/GLES Performance]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-opengles2-perf

|-
| 2D Graphics (QPainter) || Graphics Subsystem || Not Covered || || || || || ||[mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| GTK/Clutter|| Clutter || '''Light''' ||43||43 ||43 ||0% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| X (x/rendercheck) || || '''Light''' ||19||19||19||100% || [mailto:kui.zheng@intel.com Kui Zheng] || || Aug.30 2010

|-
| [[../X11 Test Specification | X11 ]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-x11

|-
| rowspan = "5" | Media Services || [[../GStreamer Test Plan | Media Framework (GStreamer)]] || Media Subsystem || '''Light''' || 260 || 260 |||| 100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan]|| Sep.10.2010

|-
| [[../Gstreamer_plugin Test Plan | Camera (Gstreamer plug-in)]] || Media Subsystem || '''Light''' || 17 || 17 ||||100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] || Sep.10.2010

|-
| Codecs (Gstreamer plug-in) || Media Subsystem || '''Light''' || Covered via Media Framework TC's || || || || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] ||

|-
| [[../PulseAudio Test Plan | Audio (PulseAudio)]] || PulseAudio || '''Light''' || 13 || 13 || 13 || 100% || [mailto:hao.h.chen@intel.com Hao Chen] || || Sep.10.2010

|-
| [[../UPnP Test Plan | GUPnP]] || Media Subsystem || '''Light''' || 25|| 25 || 25 || 0% || [mailto:daniel.tao@intel.com Daniel Tao] || ||Sept. 6 2010

|-
| rowspan = "3" | Data Management || [[../Tracker Test Plan | Content Framework (Tracker)]] || Content Framework || '''Thorough''' || 30 || 17 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang]||

|-
| [[../ContextKit Test Plan | Context Framework (ContextKit)]] || Context Framework (ContextKit) || '''Thorough''' || 15 || 5 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| Package Manager (PackageKit) || Package Manager || '''Light''' ||10 ||10 ||10 ||0% ||[mailto:huajun.li@intel.com Huajun Li] || ||Sept. 22, 2010

|-
| rowspan = "4" | Device Services || [[../Device Health Test Plan | Device Health (DSME)]] || || '''Thorough''' || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| [[../MWTS Asset Sensors Description | Sensor Framework]] || Sensor Framework || '''Average''' || 16 || 0 || ||0% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-mark.halmagiu@nokia.com Mark Halmagiu] [mailto:yi.fu@intel.com Yi Fu] || tbd
|-
| [[../Resource Manager Test Plan | Resource Manager (System Policy Manager)]] || || '''Average''' || 50 || 0 || ||tbd || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:xiaolei.zhang@intel.com Xialei Zhang]|| tbd
|-
| Backup & Restore || Backup & Restore || Open || || || |||| ||

|-
| rowspan = "3" | Personal Services || [[../PIM Test Plan | PIM services]] || PIM services || '''Average''' || 23 || 0 |||| tbd ||[mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| [[../Buteo Test Plan | Device Sync (Buteo)]] || Device Sync || '''Thorough''' || WIP || || |||| [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| Accts & SSO || || Open || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd
|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "12" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Avarage''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd
|}

Quality/TestSuite/MCTS

2010-12-08T05:43:15Z

Jerry: Undo revision 23529 by Jerry (Talk)

== MeeGo Core Test Suite (MCTS)==
=== Overview ===
INTRODUCTION 
SOURCE CODE AND COMPILING 
TEST ENVIRONMENT 
EXECUTING TESTS 
TEST RESULTS 
KNOWN ISSUES 

MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 

Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design

Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Readme ===

[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-ofono-tests/README oFono ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-connman-tests/README ConnMan ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-bluez-tests/README BlueZ ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-geoclue-tests/README GeoClue ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-piglit-tests/README 3D Graphics ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-clutter-tests/README Clutter ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-x-tests/README X ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-pulseaudio-tests/README PulseAudio ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-gupnp-tests/README GUPnP ]] 

[[/readme_template | Test Package README Template]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "5" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Startup Services || || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| Location Framework || light || || || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light || || || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||

|-
| UPnP || light || || || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| Cellular Framework || Through || || || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through || || || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| Bluetooth || Average || || || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | Graphics
| OpenGL ES || Average || || || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light || || || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] ||

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Test Suite Status For Middleware (Obsolete) ===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Bugzilla component
!|[[Quality/Plans/MeeGo_Core_Test_Plan#Test_Coverage_Definition |Test Coverage]]
!|Planned #
!|Ready #
!|In Git #
!|Auto %
!|Test Asset Maintainer
!|QA CCed
!|Availability in GIT

|-
| rowspan = "5" | Comms Services || [[../oFono Test Plan | Telephony (oFono)]] || Telephony || '''Thorough''' ||~1000||112||112||29%|| [mailto:elva.fu@intel.com Elva Fu] || ||tbd

|-
| [[../oFono Modem API Test Specification | Telephony (oFono Modem API)]] || Modem Support || '''Thorough''' ||36||36||36||tbd|| [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]|| [mailto:elva.fu@intel.com Elva Fu] || http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-ofono

|-
| [[../ConnMan Test Plan | Connection Management (ConnMan)]] || Connection Manager || '''Thorough''' ||392||392||392||44%|| [mailto:jeff.zheng@intel.com Jeff Zheng] ||||Aug.30 2010

|-
| [[../Bluetooth Test Plan | Bluetooth (BlueZ)]] || Bluetooth || '''Average''' ||60||60||60||16%|| [mailto:jingke.zhang@intel.com Jingke] || ||Aug.30 2010

|-
| [[../Telepathy Test Plan | VOIP, IM and Pres (Telepathy)]] || VoIP and IM || '''Light''' || 22 || 8 || || 0 || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] ||[mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:xiaolei.zhang@intel.com Xiaolei Zhang] || Sep.10.2010

|-
| rowspan = "4" | Internet Services || Layout Engine (WebKit) || Internet layout engine || Not Covered || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| Web RunTime (WebKit) || Web run time || Open || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| [[../Libsocialweb Test Plan | Web Services (libsocialweb)]] || Web Services || '''Thorough''' || 55 || 55 ||55 || 45% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Sept.20 2010

|-
| [[../GeoClue Test Plan | Location (GeoClue)]] || Location || '''Light''' ||30||26 ||26||100% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Aug.30 2010

|-
| rowspan = "6" | Visual Services || 3D Graphics (OpenGL/GLES) || Graphics Subsystem || '''Average''' ||1067||1067||1067||100% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| [[../OpenGLGLES Performance Test Specification | OpenGL/GLES Performance]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-opengles2-perf

|-
| 2D Graphics (QPainter) || Graphics Subsystem || Not Covered || || || || || ||[mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| GTK/Clutter|| Clutter || '''Light''' ||43||43 ||43 ||0% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| X (x/rendercheck) || || '''Light''' ||19||19||19||100% || [mailto:kui.zheng@intel.com Kui Zheng] || || Aug.30 2010

|-
| [[../X11 Test Specification | X11 ]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-x11

|-
| rowspan = "5" | Media Services || [[../GStreamer Test Plan | Media Framework (GStreamer)]] || Media Subsystem || '''Light''' || 260 || 260 |||| 100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan]|| Sep.10.2010

|-
| [[../Gstreamer_plugin Test Plan | Camera (Gstreamer plug-in)]] || Media Subsystem || '''Light''' || 17 || 17 ||||100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] || Sep.10.2010

|-
| Codecs (Gstreamer plug-in) || Media Subsystem || '''Light''' || Covered via Media Framework TC's || || || || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] ||

|-
| [[../PulseAudio Test Plan | Audio (PulseAudio)]] || PulseAudio || '''Light''' || 13 || 13 || 13 || 100% || [mailto:hao.h.chen@intel.com Hao Chen] || || Sep.10.2010

|-
| [[../UPnP Test Plan | GUPnP]] || Media Subsystem || '''Light''' || 25|| 25 || 25 || 0% || [mailto:daniel.tao@intel.com Daniel Tao] || ||Sept. 6 2010

|-
| rowspan = "3" | Data Management || [[../Tracker Test Plan | Content Framework (Tracker)]] || Content Framework || '''Thorough''' || 30 || 17 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang]||

|-
| [[../ContextKit Test Plan | Context Framework (ContextKit)]] || Context Framework (ContextKit) || '''Thorough''' || 15 || 5 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| Package Manager (PackageKit) || Package Manager || '''Light''' ||10 ||10 ||10 ||0% ||[mailto:huajun.li@intel.com Huajun Li] || ||Sept. 22, 2010

|-
| rowspan = "4" | Device Services || [[../Device Health Test Plan | Device Health (DSME)]] || || '''Thorough''' || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| [[../MWTS Asset Sensors Description | Sensor Framework]] || Sensor Framework || '''Average''' || 16 || 0 || ||0% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-mark.halmagiu@nokia.com Mark Halmagiu] [mailto:yi.fu@intel.com Yi Fu] || tbd
|-
| [[../Resource Manager Test Plan | Resource Manager (System Policy Manager)]] || || '''Average''' || 50 || 0 || ||tbd || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:xiaolei.zhang@intel.com Xialei Zhang]|| tbd
|-
| Backup & Restore || Backup & Restore || Open || || || |||| ||

|-
| rowspan = "3" | Personal Services || [[../PIM Test Plan | PIM services]] || PIM services || '''Average''' || 23 || 0 |||| tbd ||[mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| [[../Buteo Test Plan | Device Sync (Buteo)]] || Device Sync || '''Thorough''' || WIP || || |||| [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| Accts & SSO || || Open || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd
|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "12" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Avarage''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd
|}

Quality/TestSuite/MCTS

2010-12-08T05:41:21Z

Jerry: /* Test Suite Status For Middleware (New) */

== MeeGo Core Test Suite (MCTS)==
=== Overview ===
INTRODUCTION 
SOURCE CODE AND COMPILING 
TEST ENVIRONMENT 
EXECUTING TESTS 
TEST RESULTS 
KNOWN ISSUES 

MCTS Development Guideline [[/MCTS_Development_Guideline | MCTS Development Guideline]] 

Discussion about [[/MCTS_API_analysis | API analysis]] for MCTS functional test design

Interested in contributing to MCTS ? Look at [[/MCTS_Start_Contributing | How to start contributing]]

=== Test Suite Readme ===

[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-ofono-tests/README oFono ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-connman-tests/README ConnMan ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-bluez-tests/README BlueZ ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-geoclue-tests/README GeoClue ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-piglit-tests/README 3D Graphics ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-clutter-tests/README Clutter ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-x-tests/README X ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-pulseaudio-tests/README PulseAudio ]] 
[[http://gitorious.org/qa-tools/mcts/blobs/master/mcts-gupnp-tests/README GUPnP ]] 

[[/readme_template | Test Package README Template]]

=== Test Suite Code & API Coverage Analysis Repositories ===
You can get the code here: http://gitorious.org/qa-tools/mcts 
You can get the coverage analysis documents here: http://gitorious.org/qa-tools/mcts-coverage

=== MCTS Releases ===
MCTS is released typically in a biweekly cycle. The release process
is described in [[/MCTS_Release_Process | MCTS Release Process.]]

You can find information about the completed and planned MCTS releases from [[/MCTS_Releases | MCTS Releases.]]

=== Test Suite Status For Middleware (New) ===

{| cellspacing="0" border="1"
|-
!| '''Domain'''
!| '''Component'''
!| [http://wiki.meego.com/Quality/Plans/MeeGo_Core_Test_Plan Test Coverage]
!| '''% Ready'''
!| '''Auto %'''
!| [http://gitorious.org/qa-tools/mcts MCTS package]
!| '''Maintainer'''
!| '''Target Due'''
|-
| rowspan = "6" | Security

| Accounts || || || || WIP || ||

|-
| Single Sign-On || || || || WIP || ||

|-
| Integrity Protection Framework || || || || WIP || ||

|-
| Certificate Manager || || || || WIP || ||

|-
| SW Distribution Security || || || || WIP || ||

|-
| Access Control Framework || || || || WIP || ||

|-
| rowspan = "5" | System

| System Control || || || || WIP || ||

|-
| Resource Policy || Average || || || WIP || ||

|-
| Context Framework || Through || || || WIP || ||

|-
| Sensor Framework || Average || || || mcts-blts-sensor-frontend mcts-blts-sensor-plugins || ||

|-
| Location
| Location Framework || light || || || mcts-geoclue-tests || [mailto:shaofeng.tang@intel.com Shaofeng Tang] ||

|-
| rowspan = "5" | PIM

| Calendar Engine || Average || || || WIP || ||

|-
| Contacts Engine || Average || || || WIP || ||

|-
| Email Engine || Average || || || WIP || ||

|-
| Backup Framework || Average || || || WIP || ||

|-
| Synchronization Framework || Average || || || WIP || ||

|-
| rowspan = "3" | Multimedia

| Gstreamer || light || || || mcts-mwts-gstreamer mcts-mwts-gcamera || ||

|-
| PulseAudio || light || || || mcts-pulseaudio-tests mcts-blts-alsa-core || [mailto:hao.h.chen@intel.com Hao Chen] ||

|-
| UPnP || light || || || mcts-gupnp-tests || [mailto:daniel.tao@intel.com Daniel Tao] ||

|-
| rowspan = "4"| Communications
| Telephony & IM || light || || || mcts-mwts-telepathy || ||

|-
| Cellular Framework || Through || || || mcts-ofono-tests mcts-blts-ofono || [mailto:elva.fu@intel.com Elva Fu]||

|-
| [[/ConnMan Test Plan | ConnMan]] || Through || || || mcts-connman-tests || [mailto:jeff.zheng@intel.com Jeff Zheng] ||

|-
| Bluetooth || Average || || || mcts-bluez-tests mcts-blts-bluetooth || [mailto:jingke.zhang@intel.com Jingke] ||

|-
| rowspan = "3" | Qt
| Qt || || || || mcts-mwts-network mcts-mwts-telepathy || ||

|-
| Qt WebKit || || || || N/A || ||

|-
| Qt Web Runtime || || || || N/A || ||

|-
| rowspan = "9" | Qt Mobility
| QtM contacts || || || || WIP || ||

|-
| QtM Location || || || || mcts-mwts-location || ||

|-
| QtM Messaging || || || || mcts-mwts-messaging || ||

|-
| QtM Publish & Subscribe || || || || WIP || ||

|-
| QtM Sensors || || || || mcts-mwts-sensors || ||

|-
| QtM Service Framework || || || || WIP || ||

|-
| QtM Versit || || || || WIP || ||

|-
| QtM Multimedia || || || || mcts-mwts-multimedia || ||

|-
| QtM System Info || || || || WIP || ||

|-
| rowspan = "3" | Graphics
| OpenGL ES || Average || || || mcts-qtgfx-tests mcts-blts-openles2-perf || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Font Management || || || || N/A || ||

|-
| X11 || Light || || || mcts-x-tests mcts-rendercheck-tests mcts-blts-fbdev || [mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| Data Management || Content Framework || Through || || || mcts-tracker-tests || ||

|-
| SW Management
| Package Manager || light || || || mcts-packagekit-tests || [mailto:huajun.li@intel.com Huajun Li] ||

|-
| Kernel

| Linux Kernel || || || || mcts-blts-usb mcts-blts-input-devices mcts-mwts-filesystem || ||

|}

=== Test Suite Status For Middleware (Obsolete) ===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Bugzilla component
!|[[Quality/Plans/MeeGo_Core_Test_Plan#Test_Coverage_Definition |Test Coverage]]
!|Planned #
!|Ready #
!|In Git #
!|Auto %
!|Test Asset Maintainer
!|QA CCed
!|Availability in GIT

|-
| rowspan = "5" | Comms Services || [[../oFono Test Plan | Telephony (oFono)]] || Telephony || '''Thorough''' ||~1000||112||112||29%|| [mailto:elva.fu@intel.com Elva Fu] || ||tbd

|-
| [[../oFono Modem API Test Specification | Telephony (oFono Modem API)]] || Modem Support || '''Thorough''' ||36||36||36||tbd|| [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]|| [mailto:elva.fu@intel.com Elva Fu] || http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-ofono

|-
| [[../ConnMan Test Plan | Connection Management (ConnMan)]] || Connection Manager || '''Thorough''' ||392||392||392||44%|| [mailto:jeff.zheng@intel.com Jeff Zheng] ||||Aug.30 2010

|-
| [[../Bluetooth Test Plan | Bluetooth (BlueZ)]] || Bluetooth || '''Average''' ||60||60||60||16%|| [mailto:jingke.zhang@intel.com Jingke] || ||Aug.30 2010

|-
| [[../Telepathy Test Plan | VOIP, IM and Pres (Telepathy)]] || VoIP and IM || '''Light''' || 22 || 8 || || 0 || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] ||[mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:xiaolei.zhang@intel.com Xiaolei Zhang] || Sep.10.2010

|-
| rowspan = "4" | Internet Services || Layout Engine (WebKit) || Internet layout engine || Not Covered || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| Web RunTime (WebKit) || Web run time || Open || || || || || ||[mailto:huajun.li@intel.com Huajun Li] ||

|-
| [[../Libsocialweb Test Plan | Web Services (libsocialweb)]] || Web Services || '''Thorough''' || 55 || 55 ||55 || 45% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Sept.20 2010

|-
| [[../GeoClue Test Plan | Location (GeoClue)]] || Location || '''Light''' ||30||26 ||26||100% || [mailto:shaofeng.tang@intel.com Shaofeng Tang] || ||Aug.30 2010

|-
| rowspan = "6" | Visual Services || 3D Graphics (OpenGL/GLES) || Graphics Subsystem || '''Average''' ||1067||1067||1067||100% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| [[../OpenGLGLES Performance Test Specification | OpenGL/GLES Performance]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-opengles2-perf

|-
| 2D Graphics (QPainter) || Graphics Subsystem || Not Covered || || || || || ||[mailto:kui.zheng@intel.com Kui Zheng] ||

|-
| GTK/Clutter|| Clutter || '''Light''' ||43||43 ||43 ||0% || [mailto:kui.zheng@intel.com Kui Zheng] || ||Aug.30 2010

|-
| X (x/rendercheck) || || '''Light''' ||19||19||19||100% || [mailto:kui.zheng@intel.com Kui Zheng] || || Aug.30 2010

|-
| [[../X11 Test Specification | X11 ]] || || || || || || ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] |||| http://gitorious.org/qa-tools/mcts/trees/master/mcts-blts/blts-x11

|-
| rowspan = "5" | Media Services || [[../GStreamer Test Plan | Media Framework (GStreamer)]] || Media Subsystem || '''Light''' || 260 || 260 |||| 100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan]|| Sep.10.2010

|-
| [[../Gstreamer_plugin Test Plan | Camera (Gstreamer plug-in)]] || Media Subsystem || '''Light''' || 17 || 17 ||||100% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] || Sep.10.2010

|-
| Codecs (Gstreamer plug-in) || Media Subsystem || '''Light''' || Covered via Media Framework TC's || || || || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:shuang.wan@intel.com Shuang Wan] ||

|-
| [[../PulseAudio Test Plan | Audio (PulseAudio)]] || PulseAudio || '''Light''' || 13 || 13 || 13 || 100% || [mailto:hao.h.chen@intel.com Hao Chen] || || Sep.10.2010

|-
| [[../UPnP Test Plan | GUPnP]] || Media Subsystem || '''Light''' || 25|| 25 || 25 || 0% || [mailto:daniel.tao@intel.com Daniel Tao] || ||Sept. 6 2010

|-
| rowspan = "3" | Data Management || [[../Tracker Test Plan | Content Framework (Tracker)]] || Content Framework || '''Thorough''' || 30 || 17 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang]||

|-
| [[../ContextKit Test Plan | Context Framework (ContextKit)]] || Context Framework (ContextKit) || '''Thorough''' || 15 || 5 |||| tbd || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| Package Manager (PackageKit) || Package Manager || '''Light''' ||10 ||10 ||10 ||0% ||[mailto:huajun.li@intel.com Huajun Li] || ||Sept. 22, 2010

|-
| rowspan = "4" | Device Services || [[../Device Health Test Plan | Device Health (DSME)]] || || '''Thorough''' || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd

|-
| [[../MWTS Asset Sensors Description | Sensor Framework]] || Sensor Framework || '''Average''' || 16 || 0 || ||0% || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-mark.halmagiu@nokia.com Mark Halmagiu] [mailto:yi.fu@intel.com Yi Fu] || tbd
|-
| [[../Resource Manager Test Plan | Resource Manager (System Policy Manager)]] || || '''Average''' || 50 || 0 || ||tbd || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:xiaolei.zhang@intel.com Xialei Zhang]|| tbd
|-
| Backup & Restore || Backup & Restore || Open || || || |||| ||

|-
| rowspan = "3" | Personal Services || [[../PIM Test Plan | PIM services]] || PIM services || '''Average''' || 23 || 0 |||| tbd ||[mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| [[../Buteo Test Plan | Device Sync (Buteo)]] || Device Sync || '''Thorough''' || WIP || || |||| [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-lauri.poyhonen@nokia.com Lauri Pöyhönen] [mailto:jingke.zhang@intel.com Jingke Zhang] || tbd

|-
| Accts & SSO || || Open || tbd || |||| || [mailto:EXT-markku.valtonen@nokia.com Markku Valtonen] || [mailto:EXT-Juhani.taipale@nokia.com Juhani Taipale] [mailto:yi.fu@intel.com Yi Fu] || tbd
|}

=== Released Middleware Test Asset Descriptions ===
[[../MWTS Asset Descriptions | Released Middleware Test Asset Descriptions]]

=== Test Suite Status For OS Base===
{|cellspacing="0" border="1"
!|Category
!|Component
!|Test Coverage
!|Planned #
!|Ready #
!|Auto %
!|Major Contacts
!|Due

|-
| rowspan = "12" | OS Base|| [[../Audio Driver Test Specification | Audio Driver]] || '''Light''' ||31||31||0% || [mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Bluetooth Driver Test Specification | Bluetooth Driver]] || '''Light''' || 23 || 23 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Camera Driver Test Specification | Camera Driver]] || '''Light''' || 12 || 12 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen]||tbd

|-
| [[../Functional Key Driver Test Plan | Functional Key Driver]] || '''Open''' || tbd || || || || tbd

|-
| [[../GPS Driver Test Plan | GPS Driver]] || '''Light''' || || || ||Jussi Saavalainen||tbd

|-
| [[../SD-MMC Driver Test Plan | SD/MMC Driver]] || '''Light''' || 33 || 33 || 0% ||Jussi Saavalainen ||Sep.3.2010

|-
| [[../Sensor Driver Test Plan | Sensor Driver]] || '''Light''' || 8 || 8 || 0% ||Jussi Saavalainen ||tbd

|-
| [[../Touch Screen Driver Test Plan | Touch Screen Driver]] || '''Light''' || || || || Juhani Taipale||tbd

|-
| [[../Touchpad Driver Test Plan | Touchpad Driver]] || '''Open''' || tbd || || || ||tbd

|-
| [[../USB Driver Test Specification | USB Driver]] || '''Light''' || 35 || 35 || 0% ||[mailto:EXT-jussi.saavalainen@nokia.com Jussi Saavalainen] ||tbd

|-
| [[../Video Playback Driver Test Specification | Video Playback Driver]] || '''Avarage''' || 6 || 6 || 0% ||[mailto:kimmo.myllyvirta@digia.com Kimmo Myllyvirta] ||tbd

|-
| [[../WIFI Driver Test Specification | WIFI Driver]] || '''Light''' || 10 || 10 || 0% ||Jussi Saavalainen ||tbd
|}

Quality/Bugtriage

2010-11-08T12:47:21Z

Jerry: /* MeeGo Bug Triage Meetings */

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report complete
** Analyze and assign bug to proper component
** Assign bug to proper bug owner
** Set appropriate bug priority
** Adjust bug severity properly initially set by bug reporter
** Resolve obvious invalid, duplication, won’t fix bugs etc.

* 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

== Bug Triage Process ==
* Triage new incoming bugs 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/biweekly to discuss controversial bugs and any opens
Note: Whether to set up MeeGo bug triage mailing list on meego.com is still open. This could be decided later after establishing MeeGo triage team and process.

== MeeGo Bug Triage Guide ==
Check the [http://wiki.meego.com/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/jerry Jerry Yu], Peter Zhu, [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ttoropainen Tommi Toropainen], [http://meego.com/users/juhanitaipale Juhani Taipale], [http://meego.com/users/jarnoteivas Jarno Teivas]
|-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/mikikone Mika Ikonen], [http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/pekoski Petri Koski], [http://meego.com/users/ceferron Chris Ferron]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster]
|-
| MeeGo SDK Triage || TBD
|}

=== MeeGo Bug Triage Meetings ===
(MeeGo bug triage meetings to be published by end of Nov.)

* MeeGo Core Bug Triage
** Time: 1) '''Tue.''' 3:00PM PRC, 9:00AM Finland 2) '''Fri.''' TBD (suggest a Euro and American friendly time)
* MeeGo Handset Bug Triage
** Time: 1) '''Tue.''' 10:00AM Finland, 3:00PM PRC 2) '''Thu.''' 8:30AM PRC, 4:30PM US
* MeeGo Netbook Bug Triage
** Time: '''Tue.''' 9:00PM PRC, 1:00PM London
* MeeGo IVI Bug Triage
* MeeGo Translation Bug Triage
* MeeGo SDK Bug Triage

Come to join IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net] to discuss meego bug triage at any time

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [http://wiki.meego.com/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 ==
[http://wiki.meego.com/Quality/How_To_Report_Bugs How to report MeeGo bugs?]

Quality/Bugtriage Guide

2010-10-26T00:16:32Z

Jerry:

{|
| style="background: #ffcc00; color: black" | '''Note:''' This is a first and very rough draft. If you can add information please go ahead. -- [[User:Andre]]
|}

This article is for anyone who wants to help triaging the incoming and existing bug reports in MeeGo Bugzilla. This article is not for bug reporters, but those people taking a look at the reports after they have been submitted.

Following the techniques listed and explained here will help important bugs get fixed, as well as optimize precious developer time.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Sync prefixes (move from "Bugzilla" to "Quality" and update link -- [[User:Andre]]
|}

Also see [http://wiki.meego.com/Quality/How_To_Report_Bugs How To Report Bugs].

== How can I help? ==

# Create an account. The [http://bugs.meego.com bugs.meego.com] authentication system is integrated with the [http://meego.com meego.com] authentication system, so the same account is used for both sites. To create a MeeGo account visit the [http://meego.com/user/register registration page]. Soon after you will receive an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Introduce [http://wiki.maemo.org/Bugs:Stock_answers Stock answers] if wanted and agreed on -- [[User:Andre]]
|}

# Read the [Stock_answers Stock answers]. These stock responses are general examples of the kinds of comments that triagers should add to bug reports. There are even a surprising number of bug reports for which you can simply use these responses. Please always add a comment when changing the bug status to RESOLVED or NEEDINFO, so the user can comprehend your decision.
# Find what should be changed. Read the Steps of Triaging below to determine what should be changed (if anything) and how.
# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.
# Ask someone to verify your changes. In #meego-bugs on irc.freenode.net mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' editbugs permissions: Does this make any sense in the bugs.meego.com setup? -- [[User:Andre]]
|}
As time goes by and you become more familiar with Bugzilla, please ask the [http://wiki.meego.com/Quality/Bugtriage#MeeGo_Bug_Triage_Team Bugsquad members] to provide [http://www.bugzilla.org/docs/3.6/en/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.

=== Potential tasks ===

Please take a look at [http://wiki.meego.com/Quality/Bugtriage_Tasks some ideas here].

== Steps of Triaging ==

This guide should make triaging a bug as easy and simple as possible. Remember, if in doubt, ask! Also, remember that you may not be able to find anything to change for some bugs since not all bugs are filed incorrectly or incompletely.

=== Is it part of MeeGo Bugzilla? ===

Some pieces of software that users think of as part of MeeGo might be 3rd party software and have their bug tracking systems elsewhere. If the bug relates to one of these components, please close the bug as INVALID and ask the reporter to report it to the corresponding tracking system.

==== Hardware problems and Hardware enhancement requests ====

MeeGo is a software platform, hence bug reports about hardware bugs are invalid in bugs.meego.com. Please ask the reporter to either contact the hardware manufactorer (in case of Nokia this would be www.nokia.com) or to contact the company who sold the product to them.
In case of enhancement ideas for Nokia hardware there is http://conversations.nokia.com/design-by-community/.

==== Is it a valid, but wide and non-specific feature request? ====

Some reporters have great ideas and visions. They want to improve the User Experience in general or change behaviour of several applications at once.
These ideas are very hard to handle in Bugzilla as they require extensive brainstorming, discussing and involvement of several people/teams. Such reports are better to be discussed on one of the [http://meego.com/community/mailing-lists MeeGo mailing list] first .

=== Does it make sense? ===

Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should be moved to NEEDINFO state with a polite message, as should other things that are too ambiguous to be useful.
In many cases asking for a URL or attachment will help. If you need help making changes to bug fields, just comment describing what changes you want made, or ask for help from the #meego-bugs channel on Freenode IRC, or send an email to meego-qa@lists.meego.com.

=== Is the bug a duplicate? ===

Some bugs in Bugzilla have been reported before. Finding them is more of an art than a science :-) This is an important step, but don't spend too long over it; if a bug is filed twice, someone else will mark the duplicate later. Be creative, e.g. searching for "delet" will bring up all bugs that have "delete" or "deleting" in the report.
If the bug is a duplicate, mark it as a duplicate in the resolution box at the bottom of bugzilla and add a polite comment explaining that this bug/request has been filed before. You don't need to carry on triaging it if it's a duplicate; press the "Commit" button and go onto your next bug!

=== Can you reproduce it? ===

If you can, please try to reproduce the problem. If you think the problem is not reproducable, write a comment indicating the exact software version you tested, the hardware that you used, the steps you took, the results you got, and why you think the bug WORKSFORME.

=== Is the version set correctly? ===

In general we always ask people to run the latest available software release, because nobody works on fixing ancient and obsolete releases anymore.

=== Is it in the right place? ===

If you think the bug was filed against the wrong product, look for a better alternative in the drop-down list box (general information about the MeeGo architecture can be found [http://meego.com/developers/meego-architecture here]).

=== What severity/priority should be set? ===
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Document restrictions and permissions -- [[User:Andre]]
|}
The priority field is restricted to '''group_of_some_people''' so it cannot be set by reporters or changed by average users.

Finding the correct severity takes some experience, and you will get a feel for it after triaging several bugs. Here are some guidelines for the most commonly reported bugs. You should read the severity and priority guidelines at least once.

Please note that ''only'' changing severity and/or priority ''slightly'' may do more fuss than good. It causes an extra email to the maintainers and consumes their precious time and attention. If other changes are done as well then there is only little additional impact when changing severity and/or priority.

* '''Crasher bugs'''
Should have Severity=Critical.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Introduce [http://wiki.maemo.org/Bugs:Stock_answers Stock answers] if wanted and agreed on -- [[User:Andre]]
|}
Set the status to NEEDINFO if they don't have a stack trace, and ask the reporter to get a decent stack trace (see Stock_answers for more information). If there is no information about how it is triggered you should ask the original reporter how to reproduce the bug.
* '''Something not working as expected'''
Severity=Low or Medium depending on how much it breaks the application.
* '''Incorrect strings, typos, etc.'''
Severity=Low, Priority=Normal or High depending on how user-visible it is.
* '''Feature requests'''
If it really is a new feature, and not an improvement to something already in the product, set Severity=Enhancement.
If you're unsure about your Severity triage, add a comment in the bug explaining why you triaged it as you did. You can also add yourself to the CC field, so if someone retriages it differently you can find out why.

== Specific areas ==
{|
| style="background: #ffcc00; color: black" | '''TO DO: Anything needed here?'''
|}

== Acknowledgment ==

Kudos to [http://browser.garage.maemo.org/news/8/ timeless], the [http://wiki.mozilla.org/MozillaQualityAssurance:Triage Mozilla Triage Team] and the [http://live.gnome.org/Bugsquad/TriageGuide GNOME Bugsquad]. This guide is based on the [http://wiki.maemo.org/Bugs:Triage_guide maemo.org guide].

Quality/Bugtriage Guide

2010-10-26T00:15:53Z

Jerry:

{|
| style="background: #ffcc00; color: black" | '''Note:''' This is a first and very rough draft. If you can add information please go ahead. -- [[User:Andre]]
|}

This article is for anyone who wants to help triaging the incoming and existing bug reports in !MeeGo Bugzilla. This article is not for bug reporters, but those people taking a look at the reports after they have been submitted.

Following the techniques listed and explained here will help important bugs get fixed, as well as optimize precious developer time.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Sync prefixes (move from "Bugzilla" to "Quality" and update link -- [[User:Andre]]
|}

Also see [http://wiki.meego.com/Quality/How_To_Report_Bugs How To Report Bugs].

== How can I help? ==

# Create an account. The [http://bugs.meego.com bugs.meego.com] authentication system is integrated with the [http://meego.com meego.com] authentication system, so the same account is used for both sites. To create a MeeGo account visit the [http://meego.com/user/register registration page]. Soon after you will receive an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Introduce [http://wiki.maemo.org/Bugs:Stock_answers Stock answers] if wanted and agreed on -- [[User:Andre]]
|}

# Read the [Stock_answers Stock answers]. These stock responses are general examples of the kinds of comments that triagers should add to bug reports. There are even a surprising number of bug reports for which you can simply use these responses. Please always add a comment when changing the bug status to RESOLVED or NEEDINFO, so the user can comprehend your decision.
# Find what should be changed. Read the Steps of Triaging below to determine what should be changed (if anything) and how.
# Add yourself to the CC list of the reports you triage so you will receive updates and notifications on changes.
# Ask someone to verify your changes. In #meego-bugs on irc.freenode.net mention the bug number you are looking at and the changes that you think should be made. (If no one is around, it is perfectly okay to leave a comment in the relevant bug with information that could be useful to others, e.g. "I think this bug report is a duplicate of bug 1234").

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' editbugs permissions: Does this make any sense in the bugs.meego.com setup? -- [[User:Andre]]
|}
As time goes by and you become more familiar with Bugzilla, please ask the [http://wiki.meego.com/Quality/Bugtriage#MeeGo_Bug_Triage_Team Bugsquad members] to provide [http://www.bugzilla.org/docs/3.6/en/html/useradmin.html#modifyusers editbugs permissions] to you so you have gain much more power to change things and work efficiently in the bug database.

=== Potential tasks ===

Please take a look at [http://wiki.meego.com/Quality/Bugtriage_Tasks some ideas here].

== Steps of Triaging ==

This guide should make triaging a bug as easy and simple as possible. Remember, if in doubt, ask! Also, remember that you may not be able to find anything to change for some bugs since not all bugs are filed incorrectly or incompletely.

=== Is it part of MeeGo Bugzilla? ===

Some pieces of software that users think of as part of MeeGo might be 3rd party software and have their bug tracking systems elsewhere. If the bug relates to one of these components, please close the bug as INVALID and ask the reporter to report it to the corresponding tracking system.

==== Hardware problems and Hardware enhancement requests ====

MeeGo is a software platform, hence bug reports about hardware bugs are invalid in bugs.meego.com. Please ask the reporter to either contact the hardware manufactorer (in case of Nokia this would be www.nokia.com) or to contact the company who sold the product to them.
In case of enhancement ideas for Nokia hardware there is http://conversations.nokia.com/design-by-community/.

==== Is it a valid, but wide and non-specific feature request? ====

Some reporters have great ideas and visions. They want to improve the User Experience in general or change behaviour of several applications at once.
These ideas are very hard to handle in Bugzilla as they require extensive brainstorming, discussing and involvement of several people/teams. Such reports are better to be discussed on one of the [http://meego.com/community/mailing-lists MeeGo mailing list] first .

=== Does it make sense? ===

Does it have enough information? Common sense rules here - "this sucks" or "this crashed" should be moved to NEEDINFO state with a polite message, as should other things that are too ambiguous to be useful.
In many cases asking for a URL or attachment will help. If you need help making changes to bug fields, just comment describing what changes you want made, or ask for help from the #meego-bugs channel on Freenode IRC, or send an email to meego-qa@lists.meego.com.

=== Is the bug a duplicate? ===

Some bugs in Bugzilla have been reported before. Finding them is more of an art than a science :-) This is an important step, but don't spend too long over it; if a bug is filed twice, someone else will mark the duplicate later. Be creative, e.g. searching for "delet" will bring up all bugs that have "delete" or "deleting" in the report.
If the bug is a duplicate, mark it as a duplicate in the resolution box at the bottom of bugzilla and add a polite comment explaining that this bug/request has been filed before. You don't need to carry on triaging it if it's a duplicate; press the "Commit" button and go onto your next bug!

=== Can you reproduce it? ===

If you can, please try to reproduce the problem. If you think the problem is not reproducable, write a comment indicating the exact software version you tested, the hardware that you used, the steps you took, the results you got, and why you think the bug WORKSFORME.

=== Is the version set correctly? ===

In general we always ask people to run the latest available software release, because nobody works on fixing ancient and obsolete releases anymore.

=== Is it in the right place? ===

If you think the bug was filed against the wrong product, look for a better alternative in the drop-down list box (general information about the MeeGo architecture can be found [http://meego.com/developers/meego-architecture here]).

=== What severity/priority should be set? ===
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Document restrictions and permissions -- [[User:Andre]]
|}
The priority field is restricted to '''group_of_some_people''' so it cannot be set by reporters or changed by average users.

Finding the correct severity takes some experience, and you will get a feel for it after triaging several bugs. Here are some guidelines for the most commonly reported bugs. You should read the severity and priority guidelines at least once.

Please note that ''only'' changing severity and/or priority ''slightly'' may do more fuss than good. It causes an extra email to the maintainers and consumes their precious time and attention. If other changes are done as well then there is only little additional impact when changing severity and/or priority.

* '''Crasher bugs'''
Should have Severity=Critical.

{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Introduce [http://wiki.maemo.org/Bugs:Stock_answers Stock answers] if wanted and agreed on -- [[User:Andre]]
|}
Set the status to NEEDINFO if they don't have a stack trace, and ask the reporter to get a decent stack trace (see Stock_answers for more information). If there is no information about how it is triggered you should ask the original reporter how to reproduce the bug.
* '''Something not working as expected'''
Severity=Low or Medium depending on how much it breaks the application.
* '''Incorrect strings, typos, etc.'''
Severity=Low, Priority=Normal or High depending on how user-visible it is.
* '''Feature requests'''
If it really is a new feature, and not an improvement to something already in the product, set Severity=Enhancement.
If you're unsure about your Severity triage, add a comment in the bug explaining why you triaged it as you did. You can also add yourself to the CC field, so if someone retriages it differently you can find out why.

== Specific areas ==
{|
| style="background: #ffcc00; color: black" | '''TO DO: Anything needed here?'''
|}

== Acknowledgment ==

Kudos to [http://browser.garage.maemo.org/news/8/ timeless], the [http://wiki.mozilla.org/MozillaQualityAssurance:Triage Mozilla Triage Team] and the [http://live.gnome.org/Bugsquad/TriageGuide GNOME Bugsquad]. This guide is based on the [http://wiki.maemo.org/Bugs:Triage_guide maemo.org guide].

Quality/Bugtriage

2010-10-23T08:28:47Z

Jerry: /* MeeGo Bug Triage Team */

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report complete
** Analyze and assign bug to proper component
** Assign bug to proper bug owner
** Set appropriate bug priority
** Adjust bug severity properly initially set by bug reporter
** Resolve obvious invalid, duplication, won’t fix bugs etc.

* 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

== Bug Triage Process ==
* Triage new incoming bugs 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/biweekly to discuss controversial bugs and any opens
Note: Whether to set up MeeGo bug triage mailing list on meego.com is still open. This could be decided later after establishing MeeGo triage team and process.

== MeeGo Bug Triage Guide ==
Check the [http://wiki.meego.com/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/jerry Jerry Yu], Peter Zhu, [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ttoropainen Tommi Toropainen], [http://meego.com/users/juhanitaipale Juhani Taipale], [http://meego.com/users/jarnoteivas Jarno Teivas]
|-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/mikikone Mika Ikonen], [http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/pekoski Petri Koski], [http://meego.com/users/ceferron Chris Ferron]
|-
| MeeGo Netbook UX Triage || Ling Yu, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster]
|-
| MeeGo SDK Triage || TBD
|}

=== MeeGo Core Bug Triage ===
IRC meetings '''do not exist yet'''. They are planned for to take place on IRC in the channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

Time: 1) '''Tue.''' 2:00PM PRC, 9:00AM Finland 2) '''Fri.''' 2:30PM PRC, 9:30AM Finland

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [http://wiki.meego.com/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 ==
[http://wiki.meego.com/Quality/How_To_Report_Bugs How to report MeeGo bugs?]

Quality/defects

2010-10-18T08:22:37Z

Jerry: /* MeeGo In-Vehicle Infotainment */

== MeeGo 1.1 Defects Management ==
=== MeeGo Core ===
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Open&sharer_id=234 '''Open Bugs''']
* '''1.1 Release Blocker'''
** [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Proposed&sharer_id=234 '''Proposed'''] and waiting for review
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Approved&sharer_id=234 '''Accepted'''] (Still [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Approved_Open&sharer_id=234 '''Open'''])
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Rejected&sharer_id=234 '''Rejected''']

=== MeeGo Handset ===
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_HandsetUX_Open&sharer_id=234 '''Open Bugs''']
* '''1.1 Release Blocker'''
** [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_HandsetUX_Proposed&sharer_id=234 '''Proposed'''] and waiting for review
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_HandsetUX_Approved&sharer_id=234 '''Accepted'''] (Still [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_HandsetUX_Approved_Open&sharer_id=234 '''Open'''])
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_HandsetUX_Rejected&sharer_id=234 '''Rejected''']

=== MeeGo Netbook ===
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_NetbookUX_Open&sharer_id=234 '''Open Bugs''']
* '''1.1 Release Blocker'''
** [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_NetbookUX_Proposed&sharer_id=234 '''Proposed'''] and waiting for review
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_NetbookUX_Approved&sharer_id=234 '''Accepted'''] (Still [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_NetbookUX_Approved_Open&sharer_id=234 '''Open'''])
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_NetbookUX_Rejected&sharer_id=234 '''Rejected''']

=== MeeGo In-Vehicle Infotainment ===
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_IVI_Open&sharer_id=234 '''Open Bugs''']

Quality/defects

2010-10-09T06:40:40Z

Jerry: /* MeeGo Core */

Quality/defects

2010-10-09T06:38:40Z

Jerry: Created page with "== MeeGo 1.1 Defects Management == === MeeGo Core === * [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Open&sharer_id=234 Open Bugs] * [http://b…"

== MeeGo 1.1 Defects Management ==
=== MeeGo Core ===
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Open&sharer_id=234 Open Bugs]
* [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_NewInLast7Days&sharer_id=234 New Bugs] reported in the past 7 days, [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_NewInLast7Days_Undecided&sharer_id=234 Undecided]
* '''1.1 Release Blocker'''
** [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Proposed&sharer_id=234 '''Proposed'''] and waiting for review
** Reviewed and [http://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=1.1_Core_Approved&sharer_id=234 '''Accepted''']
=== MeeGo Handset ===
=== MeeGo Netbook ===
=== MeeGo In-Vehicle Infotainment ===

Quality

2010-10-09T06:34:36Z

Jerry: /* Defect tracking */

= Quality =

WORK IN PROGRESS - ''This page is placeholder collecting MeeGo Quality Assurance material - please refer to [http://meego.com/community meego-community] and [http://forum.meego.com forum.meego.com] for QA discussion''

== QA Tools ==

=== MeeGo QA tools team ===

Meet the quality assurance team and participate in activities. You are most welcome!

[[Quality/QA-tools|MeeGo QA tools team]]

=== Test packaging ===

[[Quality/QA-tools/Test_Packaging|Test packaging]] is mechanism to wrap any tests in rpm packages to automate execution.

=== Test Case Management Tool ===

[[Quality/testmanagementtool|Test Case Management Tool]] - we will setup and evaluate testlink for test case management.

=== Autotest-guide ===
[[Quality/QA-tools/Autotest-guide|Autotest-Guide]] - A guide for setting up automated testing environment. Includes instructions how to automate test execution and image installations and information on tools used in test automation.

=== OTS - Open Testing System ===

[[Quality/QA-tools/OTS|OTS]] provides the infrastructure for automatic test execution.

== Procedures and best practices ==

* [[Quality/TestabilityChecklist|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/QualityConsiderations|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.

* [[Quality/TestAreas| Short descriptions for Test Areas/Types]]

*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 

== Testing ==

Help us by specifying and executing tests
* [[TestPlanTemplate|Test Plan Template]] -- WORK IN PROGRESS, please contribute
** high level test cases (aka test ideas) and low level test cases shall be listed in detailed test plans
** Some ideas/intent for Test Execution management can be found from [[Talk:TestPlanTemplate]]
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[TestReportTemplateCollection|Test Report Template]] -- WORK IN PROGRESS, pls. contribute
* [[TestCaseTemplate|Test Case Template]] -- WORK IN PROGRESS, pls. contribute
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]

=== MeeGo Core Testing ===
* [[/TestPlan/MeeGo Core Test Plan | MeeGo Core Test Plan]]
* [[/TestabilityStatus | Core OS Testability Status]]
* [[/TestSuite/MCTS | MeeGo Core Test Suite (MCTS)]]
* [[/CoreTestReports | Core Testing Reports]]
* [[/Defects/Core | Core Defects]]

=== MeeGo Handset Testing ===
* [http://wiki.meego.com/Quality/1.1HandsetUXTestPlan MeeGo HandSet UX Test Plan] (for 1.1)
** [http://wiki.meego.com/Quality/HandSetUXRamp-Up1.1 QA Ramp-Up Schedule]
* [http://wiki.meego.com/Quality/HandsetUXTestPlan MeeGo HandSet UX Test Plan] - Generic HandSet UX QA test plan. Valid from MeeGo HandSet UX 1.2 release and onwards.
** [http://wiki.meego.com/Quality/HandSetUXRamp-Up1.2 QA Ramp-Up Schedule for 1.2]
* [http://wiki.meego.com/Quality/HandsetTestabilityStatus Testability Status Report]
* [http://wiki.meego.com/Quality/HandsetTestSuite Test Suite]
* [http://wiki.meego.com/Quality/HandsetTestReport Test Report]
* [http://wiki.meego.com/Quality/HandsetQualityMetrics Quality Metrics]

=== MeeGo Netbook Testing ===

==== Test Suites & Utilities ====
[[Quality/Netbook_Test_Suite_and_Utilities|Test Suites and Utilities]] - Here are some available test suites and utilities. Welcome download and contribute.

==== MeeGo 1.0 Software Update Testing ====
* [[1.0SWUpdateTestPlan|Test Plan]] describes the test strategy, test approach, checkpoints and etc of software update testing for MeeGo 1.0 Netbook
* Test Report
** Welcome your contribution! You are encouraged to refer to the [[1.0SWUpdateTestPlan|Test Plan]] and follow [[TestReportTemplateCollection|Test Report Template]]
** [[1.0SWUpdateTestReport|Test Report Archive]]: Please upload your test reports here.

==== MeeGo 1.1 ====
* Test Plan
* Test Suite
* [[1.1NetbookTestReport|Test Report]]

=== MeeGo SDK Testing ===
* [[SDKTestPlan|Test Plan]] describes the test strategy, test approach, checkpoints and etc of MeeGo SDK
* Test Suite
* [[/SDKTestReports | Test Report]]

== Defect tracking ==
* [[/defects | Defects Management]]
* [[/Bugtriage | MeeGo Bug Triage]]
* [http://wiki.meego.com/Bugzilla/how-report-bugs How to report bugs]
* [http://wiki.meego.com/MeeGoBugzilla_Customization Bugzilla customized features]

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

Bugzilla/how-report-bugs

2010-09-27T01:56:02Z

Jerry: /* Priority */

=Getting started=
All you need is an account to be able to file and comment on reports. The http://bugs.meego.com authentication system is integrated with the http://meego.com authentication system, so the same account is used for both sites. To create a MeeGo account visit the [http://meego.com/user/register registration page]. Soon after you will reveice an email with a link that must be visited to confirm your account creation. You will have to change your password on meego.com before attempting to log into Bugzilla.

=Bugzilla Fields=
==MeeGo Release==

MeeGo Release field defines in which MeeGo version a bug has been found. Version names are defined according to the [http://wiki.meego.com/Release_Engineering/Plans MeeGo release plan].

==Target Milestone==

When bugs are in OPEN or RESOLVED status, it is used by the bug reporter to propose which milestone this bug is expected to be fixed.

* --- Undecided
* 1.0 Propose bug is expected to be fixed in 1.0
* 1.1 Propose bug is expected to be fixed in 1.1

==Importance==
===Priority===
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Content differs from [http://bugs.meego.com/page.cgi?id=fields.html Bugzilla]; two places for explaining this
|}

Priority field describes the importance and order in which a bug should be fixed. It helps developers to prioritize their work. By default the priority is set as "Undecided" when reporting a new bug. The bug reporter could propose a priority in a comment. A dedicated bug triage team should set the initial priority for the bug while processing it as early as possible. Final priority setting would be decided by bug triage process. Priorities range from High (most important) to Low (least important).
* High: Bug fixing is on-going, or is planned within 2 weeks, no later than the up-coming milestone. Reproducible crash issues, major function loss, issues greatly impact user experience or issues which block other key features to work would fall in to this category.
* Medium: Bug fixing is planned before project release, but can't start before HIGH priority items are cleaned up.
* Low: Bug fixing is not planned for the up-coming project release. Will re-evaluate the importance in next release.

===Severity===
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Content contradicts with [http://bugs.meego.com/page.cgi?id=fields.html Bugzilla]; two places for explaining this
|}
The "Severity" field describes the impact of a bug, and the options include:

* Critical: crashes, other components are affected
* Major: major loss of own function
* Normal: regular issue, some loss of functionality under specific circumstances
* Minor: minor loss of function, or other problem, where an easy workaround is present
* Enhancement: request for enhancement

==Platform==
===Hardware===
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Content differs from [http://bugs.meego.com/page.cgi?id=fields.html Bugzilla]; two places for explaining this
|}
Please select the UX (like Netbook, Nettop, Notebook, Handset, Automotive, TV) that you identified the bug in.
For bugs which apply to all UX (like bugs for Middleware/Core components), please select "All".

===Architecture===

Please select the architecture (IA, ARM) that you identified the bug in. For example for N900 Base OS layer bugs this should be set to ARM.
For bugs which apply for multiple architectures, like bugs for middleware or applications, please select "All".

= Bug Life Cycle =
[[file:Bug-life-cycle.PNG]]

= Bug Reporting/Follow-up Guideline =
{|
| style="background: #ffcc00; color: black" | '''TO DO:''' Content duplicated/differs from [https://bugs.meego.com/page.cgi?id=bug-writing.html Bugzilla]; two places for explaining this
|}
1. Each bug report is for only one issue. If you find several issues in one test, please separate them into several bugs.

2. Write a precise summary (bug title). A good summary should be straightforward and precise, to clearly identify the issue.

3. List the exact steps to reproduce the bug (bash commands, results after executing the commands etc, instead of only paraphrasing). For example, instead of paraphrasing commands by saying:
"suspend the system or put system to S3"
we prefer to see the following exact commands as steps to reproduce the bug:
echo mem >/sys/power/state

4. Reproducibility. For bugs which are not 100% reproducible, please provide an estimate of the probability of reproduction.

5. Impact to system or user. Provide a description of the actual impact to the system or user.

6. DO NOT reopen if same defect found again after more than 2 weeks. New bug report with “[REG]” as a prefix in the summary is mandatory.

7. NEEDINFO bugs should be assigned back to original bug reporter and NEEDINFO status should be removed after requested missing data has been provided in the report. NEEDINFO status should only be used for requests against the original bug reporter.

8. For "Target Milestone", when reports are in OPEN or RESOLVED status, it means to propose the bug to get fixed for a particular release; When verifying bugs, set the correct milestone where the bug is fixed.

= Guidelines =
We like to have fun but we also like the communications to run smoothly. To that end here are some guidelines for participating in [https://bugs.meego.com Bugzilla].

==Do be patient with others==
We have both techies and non-techies here and we both know we don't exactly speak the same language at all times. In case of missing information kindly tell reporters how to provide it, and/or point to https://bugs.meego.com/page.cgi?id=bug-writing.html in case of very vague reports (like "Can't send mail, plz help!!").

==Do search before you file a bug==
Try to avoid filing duplicates by [http://bugs.meego.com/query.cgi taking a look] whether your issue has already been filed before.

==Keep it clean==
Don't start endless debates on topics not directly related to the scope of a specific bug report, for example release engineering or marketing. There is [http://forum.meego.com/ the forum] for that.
Avoid quoting complete previous comments by stripping unneeded lines. Avoid answering above the quoted text.

==The admins Rule==
Ultimately, the admins reserve the right to block your account. See our [[Community guidelines|process for dealing with violations]] for more details.

= How to get involved =
As a non-coder you can get involved by [http://bugs.meego.com/enter_bug.cgi reporting bugs] and [http://wiki.meego.com/Quality/Bugtriage triaging bug reports].

Quality/Plans/MeeGo Core Test Plan

2010-09-08T11:32:21Z

Jerry: /* Daily Auto Testing */

'''Draft only. It's under active revising and updating'''
= MeeGo Core Overall Test Plan =

== Scope of this Document ==
This is overall test plan for MeeGo Core of '''MeeGo open source project''', which defines test scope, test strategy, test configurations as well as test execution cycle for MeeGo Core. It will give readers an overview of validation activities for MeeGo Core of MeeGo open source releases. A series of component test plans will also be linked in this overall test plan to cover the detailed test approaches and test design for ingredients of MeeGo Core stack. It will be the joint effort from Nokia, Intel and MeeGo community.

== Features to Be Tested ==
Overall the MeeGo Core Testing will cover the '''MeeGo OS Middlewares layer''' and '''MeeGo OS Base layer''' in [http://meego.com/developers/meego-architecture MeeGo Architecture]:
[[File:MeeGoArch.png]]

Specific features to be tested will be aligned with the features under '''MeeGo Core OS Features''' product in [http://bugs.meego.com MeeGo Featurezilla]

== What will not Be Tested ==
Following feature category won't be covered in MeeGo Core validation for MeeGo open source releases.
* Any proprietary component which is not included in the open source MeeGo release
* Certification testing like: Ofono and Bluetooth

== Test Strategy and Approach ==
The overall objective of MeeGo Core testing is to ensure MeeGo middlewares provide stable hardware and usage model independent application services and APIs for building the vertical specific user experience. Each core component has different quality risk regarding to MeeGo integration. For example, some core component is mature in upstream and MeeGo do the integration without heavy new feature development; some component is contributed and open-sourced from proprietary component with heavy development. Considering most of MeeGo Core components will be adopted by multiple vertical usages and run on a number of MeeGo devices, we also need to take test execution efficiency into account when creating the test cases. Given this, we have below strategy considerations:
* Create one unified test suite (MeeGo Core Test Suite) for MeeGo Core validation. It's open-sourced and could start with the first batch of test cases contributed from Nokia and Intel, and will continually grow with the contribution from community. You can find the MeeGo Core Test Suite (MCTS) docs at [http://wiki.meego.com/Quality/TestSuite/MCTS MeeGo Quality] page, and the code in [http://gitorious.org/qa-tools/release-tests, Gitorious].
* Define appropriate test coverage (density) categories. The test coverage of each component is based on the quality risk regarding to MeeGo integration.
* Automate test cases as many as possible and be able to run under MeeGo auto testing framework.
* MeeGo Core test cases won't depend on vertical specific UX
=== Test Coverage Definition ===
In order to use resources efficiently and control risk level on component maturity. Testing is done in different levels as follows:

* '''Thorough'''
** Full testing service for API
** Target is to have 100% function/method coverage provided by API
** Parameter coverage defined by using testing techniques as follows:
*** All Pairs (Pair wise)
*** Equivalence Partitioning
*** Boundary Value Analysis
*** Subjective test case selection (according to Expert opinion or similar)

* '''Average'''
** Between Thorough and Light
** Full API coverage (according to rules for Thorough) for new functionality.
** Integration level testing for legacy features.

* '''Light'''
** Integration level testing
** Upstream Middleware components shall be tested with limited amount of test cases (sub set) ensuring that integration of component to MeeGo is successful and component is working as expected

* '''Not Covered'''
** No Middleware testing, covered indirectly by UX Testing
** There will be API’s not feasible to cover with test cases at middleware level but more efficiently tested indirectly by UX testing

=== Component Test Plans and Coverage ===
Go to [[../../TestSuite/MCTS#Test_Suite_Status_For_Middleware |MeeGo Core Test Suite]] for details

=== Test Cycle ===
MeeGo Core will be tested from the following different test execution levels.
==== Hourly Testing ====
It's for Trunk:Testing. It will run a portion of fully automated test cases for core components and aims to provide quick acceptance testing to support incremental packages integration. It will be conducted under OTS (Open Test System).

==== Daily Auto Testing ====
It's for Trunk. It will run all fully automated test cases for core components and aims to identify the regressions as early as possible. It will be conducted under OTS (Open Test System).

==== Weekly Testing ====
Weekly Testing is a test cycle against the weekly images released from distribution team. Usually the test frequency is twice a week, which aligns with distribution's weekly image release cadence.

It's an incremental testing and includes two parts in general: test the basic distribution health to report out regression, test new features when they are ready for testing. We will also do bug verification and regression test which is set of tests to verify that changes from the last build (code enhancements, bug fixes) don't introduce new issues to the previous working code. The purpose of weekly testing is to early test the new features, to track critical/major issues got fixed in timely fashion, and to report out the overall quality status of the whole image so that people could understand where we are.

==== Milestone Testing ====
In the formal test cycle for milestone test, after a new build passed the BAT test, test team will start the full validation testing for it, following test will be involved:
* Functional Test – which will follow the component test plan to run all tests.
* Non Functional Test – which are defined in the individual component test plan.

==== Regression Testing ====
This is a set of tests to verify that changes from the last build (code enhancements, bug fixes) don’t introduce new issues to the previous working code as well as new features work as expected. This cycle include the tests for previous major bug fixes and areas of the code that will be affected by new implementation.

The regression test will be taken in following test cycle:
* In the test cycle for milestone release, before the release criteria is satisfied, it is possible that there are several release candidates which includes bug fixes for previous release candidates. These bug-fixes need be tested
* In the intermediate regular release, only the modified features need to be heavily tested.
* Bug verification on weekly basis to make sure the bug fixes be verified within one week after bug fixing

=== Test Report ===
* Send Test report to mailing list
** Weekly MeeGo Core Test Report (Bug verification, new feature exploration...)
** Distribution Milestone Full Pass Test report
* Archive reports at [http://wiki.meego.com/Quality/CoreTestReports MeeGo Quality] wiki

== Environmental Needs ==
=== Hardware Platforms ===
'''MeeGo v1.1'''
* Aava Koski
* N900
* MRST CDK
* Netbook

=== Peripherals required ===
{|cellspacing="0" border="1"
!| Category || Peripherals
|-
| Wireless || Wireless AP (abg)
|-
| Bluetooth Devices || Bluetooth dangles, Bluetooth keyboard, Bluetooth mouse,Bluetooth phone headset, Bluetooth A2DP headset
|-
| USB devices || Camera, keyboard, mouse, USB storage device , microphone, ...
|-
| 3G || 3G modem and Sim Card
|-
| SD Card || 1G/2G/4G
|-
| MMC Card || 512M/1G/2G
|-
| Speaker || 5.1
|}

=== Network Environment ===
The networking arrangements needed to conduct the testing:
* LAN
* WiFi network (abg)
* Internet
* 3G network
== References ==
* MCTS (MeeGo Core Test Suite) code git tree: http://gitorious.org/qa-tools (to be moved meego.gitorious.org)
* MCTS docs http://wiki.meego.com/Quality/TestSuite/MCTS
* MeeGo Architecture: http://meego.com/developers/meego-architecture
* MeeGo Core test reports archive: http://wiki.meego.com/Quality/CoreTestReports
* MeeGo bugzilla: http://bugs.meego.com