MeeGo wiki - User contributions [en]

Quality/1.2.0 IVI Update Test Plan

2011-10-19T06:26:16Z

Shuangeeer: /* Test Report */

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Checkpoints ===
Note: '''checkpoint''' in bold means it is also a sanity test point.

{|cellspacing="0" border="1"
!|Category
!|Checkpoints
|-
|System Overall
|
* [''Startup''] Liveboot/'''boot from local disk'''
* [''Installation''] Installer/Installer-shell launch and launch time
* [''Installation''] '''Installation in text mode and system start up(installer removal)'''
* [''Installation''] Installation in GUI mode and system start up(installer removal)
* [''Peripherals''] USB/SD auto-mounter/read/write
* [''AppManager''] '''Zypper install'''/update/debuginfo-install/source-install default repo configuration
* [''AppManager''] pkcon install/update
* [''Settings''] date&time settings
* [''Settings''] system build ID
* [''Pnp''] '''Cold boot time'''
* [''Pnp''] Powertop log analysis, Cn state, avg resident, Wakeup times
* [''Stability''] Shutdown and Reboot system 10 times without failure or crash
* [''Stability''] Use multiple applications
|-
|Hardware Adaptation
|
* ML7213 drivers
* EG20T drivers
* '''touch screen'''
* '''Ethernet'''
* Wifi
* '''snd card'''
* onboard MMC
* '''removable MMC/USB'''
* '''USB HID'''/hub/LAN/BT dangle
* '''dmesg'''
|-
|Graphics Driver(EMGD)
|
* '''System Startup with EMGD enabled'''
* startx from console
* Switch between X/console
* '''Desktop rendering'''
* GUI installer rendering
* Check basic 3D application glxgears can be run successfully
* '''Single(LVDS) display'''
|-
|Connectivity/Communication
|
* '''Ethernet connection'''/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, '''HFP''')
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* '''gstreamer play audio/video'''
|-
|XFCE desktop
|
* '''Desktop render'''
* XFCE menu view
* '''app launch/close/switch'''
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
** CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
** BIOS: AMI 4.6.3.7/0ABXJ 0.03
** Display: 7’’ LVDS
** Hard drive: SATA SSD 8G
* Crown Bay
** Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
** BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
** Display = 13’’ LVDS
** Hard drive: SATA HD 160G
** wifi card: Intel wifi link 5100

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* Milestone Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

Quality/1.2.0 IVI Update Test Plan

2011-10-19T05:07:20Z

Shuangeeer: /* Checkpoints */

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Checkpoints ===
Note: '''checkpoint''' in bold means it is also a sanity test point.

{|cellspacing="0" border="1"
!|Category
!|Checkpoints
|-
|System Overall
|
* [''Startup''] Liveboot/'''boot from local disk'''
* [''Installation''] Installer/Installer-shell launch and launch time
* [''Installation''] '''Installation in text mode and system start up(installer removal)'''
* [''Installation''] Installation in GUI mode and system start up(installer removal)
* [''Peripherals''] USB/SD auto-mounter/read/write
* [''AppManager''] '''Zypper install'''/update/debuginfo-install/source-install default repo configuration
* [''AppManager''] pkcon install/update
* [''Settings''] date&time settings
* [''Settings''] system build ID
* [''Pnp''] '''Cold boot time'''
* [''Pnp''] Powertop log analysis, Cn state, avg resident, Wakeup times
* [''Stability''] Shutdown and Reboot system 10 times without failure or crash
* [''Stability''] Use multiple applications
|-
|Hardware Adaptation
|
* ML7213 drivers
* EG20T drivers
* '''touch screen'''
* '''Ethernet'''
* Wifi
* '''snd card'''
* onboard MMC
* '''removable MMC/USB'''
* '''USB HID'''/hub/LAN/BT dangle
* '''dmesg'''
|-
|Graphics Driver(EMGD)
|
* '''System Startup with EMGD enabled'''
* startx from console
* Switch between X/console
* '''Desktop rendering'''
* GUI installer rendering
* Check basic 3D application glxgears can be run successfully
* '''Single(LVDS) display'''
|-
|Connectivity/Communication
|
* '''Ethernet connection'''/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, '''HFP''')
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* '''gstreamer play audio/video'''
|-
|XFCE desktop
|
* '''Desktop render'''
* XFCE menu view
* '''app launch/close/switch'''
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
** CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
** BIOS: AMI 4.6.3.7/0ABXJ 0.03
** Display: 7’’ LVDS
** Hard drive: SATA SSD 8G
* Crown Bay
** Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
** BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
** Display = 13’’ LVDS
** Hard drive: SATA HD 160G
** wifi card: Intel wifi link 5100

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* System Use Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

MeeGo IVI Test Suite

2011-10-19T04:57:13Z

Shuangeeer: /* Test Suite Overview */

= MeeGo IVI Test Suite =
MeeGo IVI Test Suite is the test suite for testing MeeGo IVI, and short for ''MITS''.

== Test Suite Overview ==
Latest MITS source code is available at http://meego.gitorious.org/meego-quality-assurance/mits.
There are NN categories in MITS corresponding to each domain/component of MeeGo IVI.

{| cellspacing="0" border="1"
! Test set
! Description
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-connectivity-tests mits-connectivity-tests] || Test set about Ethernet, Wifi and Bluetooth
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-graphics-tests mits-graphics-tests] || Test set about Graphics driver on IVI (EMGD)
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-hfdialer-tests mits-hfdialer-tests] || Test set about Hands Free Dialer
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-hwadaptation-tests mits-hwadaptation-tests] || Test set about Hardware Adaptation for IVI
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-navigation-tests mits-navigation-tests] || Test set about Navigation
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-sanity-tests mits-sanity-tests] || Sanity Test set
|-
|}

== How to build and install MITS ==
Suppose you're going to install test set mits-connectivity-tests in MITS.
# export http_proxy=<proxy> if you are in Intranet
git clone http://git.gitorious.org/meego-quality-assurance/mits.git
cd mits/mits-connectivity-tests
./pack.sh
# You need make sure that you have already installed necessary build required packages.
# If packaging is successful, there will be rpm pkgs(x86.rpm, src.rpm, tar.gz) generated.
rpm -ivh mits-connectivity-tests.<version>.rpm
# You need make sure that you have already installed required packages

== How to run MITS ==
With MeeGo default release repo, install package ''testrunner-lite''.

zypper in testrunner-lite

/usr/share/<test suite name>/tests.xml defines all test cases for the test suite. You can run all test cases in the test suite using testrunner-lite. You need to define where the test result is.

testrunner-lite -a -f /usr/share/<test suite name>/tests.xml -o results.xml

Follow the steps specified in each case and fill the results as well.

Note: By default, MITS test suite needs to be run with root user

== Maintainer ==
[mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

MeeGo IVI Test Suite

2011-10-19T03:39:17Z

Shuangeeer: /* Test Suite Overview */

= MeeGo IVI Test Suite =
MeeGo IVI Test Suite is the test suite for testing MeeGo IVI, and short for ''MITS''.

== Test Suite Overview ==
Latest MITS source code is available at http://meego.gitorious.org/meego-quality-assurance/mits.
There are NN categories in MITS corresponding to each domain/component of MeeGo IVI.

{| cellspacing="0" border="1"
! Test set
! Description
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-connectivity-tests mits-connectivity-tests] ||
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-graphics-tests mits-graphics-tests] ||
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-hfdialer-tests mits-hfdialer-tests] ||
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-hwadaptation-tests mits-hwadaptation-tests] ||
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-navigation-tests mits-navigation-tests] ||
|-
| [http://meego.gitorious.org/meego-quality-assurance/mits/trees/master/mits-sanity-tests mits-sanity-tests] ||
|-
|}

== How to build and install MITS ==
Suppose you're going to install test set mits-connectivity-tests in MITS.
# export http_proxy=<proxy> if you are in Intranet
git clone http://git.gitorious.org/meego-quality-assurance/mits.git
cd mits/mits-connectivity-tests
./pack.sh
# You need make sure that you have already installed necessary build required packages.
# If packaging is successful, there will be rpm pkgs(x86.rpm, src.rpm, tar.gz) generated.
rpm -ivh mits-connectivity-tests.<version>.rpm
# You need make sure that you have already installed required packages

== How to run MITS ==
With MeeGo default release repo, install package ''testrunner-lite''.

zypper in testrunner-lite

/usr/share/<test suite name>/tests.xml defines all test cases for the test suite. You can run all test cases in the test suite using testrunner-lite. You need to define where the test result is.

testrunner-lite -a -f /usr/share/<test suite name>/tests.xml -o results.xml

Follow the steps specified in each case and fill the results as well.

Note: By default, MITS test suite needs to be run with root user

== Maintainer ==
[mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

MeeGo IVI Test Suite

2011-10-19T03:32:09Z

Shuangeeer: /* How to build and install MITS */

MeeGo IVI Test Suite

2011-10-19T03:31:04Z

Shuangeeer: Created page with "= MeeGo IVI Test Suite = MeeGo IVI Test Suite is the test suite for testing MeeGo IVI, and short for ''MITS''. == Test Suite Overview == Latest MITS source code is available at ..."

Quality

2011-10-19T03:16:00Z

Shuangeeer: /* Projects */

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [[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]]
|
* [[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]]
|
* [[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]
|
* [[Quality/1.2.0_IVI_Update_Test_Plan|1.2.0 Update Test Plan]]
* [[MeeGo IVI 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|Find our tools and contact information]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

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

== 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.

== Tasks of the "QA Contact" ==

* QA contact work with/support/advice/help package maintainers (see [http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility|Fedora example] or [[Packaging/Guidelines#Maintaining_a_Package|MeeGo guidelines for maintaining 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 [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Handling page]])
*** 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/1.2.0 IVI Update Test Plan

2011-10-19T03:05:02Z

Shuangeeer: /* Checkpoints */

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Checkpoints ===
Note: '''checkpoint''' in bold means it is also a sanity test point.

{|cellspacing="0" border="1"
!|Category
!|Checkpoints
|-
|System Overall
|
* [''Startup''] Liveboot/'''boot from local disk'''
* [''Installation''] Installer/Installer-shell launch and launch time
* [''Installation''] '''Installation in text mode and system start up(installer removal)'''
* [''Installation''] Installation in GUI mode and system start up(installer removal)
* [''Peripherals''] USB/SD auto-mounter/read/write
* [''AppManager''] '''Zypper install'''/update/debuginfo-install/source-install default repo configuration
* [''AppManager''] pkcon install/update
* [''Settings''] date&time settings
* [''Pnp''] '''Cold boot time'''
* [''Pnp''] Powertop log analysis, Cn state, avg resident, Wakeup times
* [''Stability''] Shutdown and Reboot system 10 times without failure or crash
* [''Stability''] Use multiple applications
|-
|Hardware Adaptation
|
* ML7213 drivers
* EG20T drivers
* '''touch screen'''
* '''Ethernet'''
* Wifi
* '''snd card'''
* onboard MMC
* '''removable MMC/USB'''
* '''USB HID'''/hub/LAN/BT dangle
* '''dmesg'''
|-
|Graphics Driver(EMGD)
|
* '''System Startup with EMGD enabled'''
* startx from console
* Switch between X/console
* '''Desktop rendering'''
* GUI installer rendering
* Check basic 3D application glxgears can be run successfully
* '''Single(LVDS) display'''
|-
|Connectivity/Communication
|
* '''Ethernet connection'''/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, '''HFP''')
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* '''gstreamer play audio/video'''
|-
|XFCE desktop
|
* '''Desktop render'''
* XFCE menu view
* '''app launch/close/switch'''
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
** CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
** BIOS: AMI 4.6.3.7/0ABXJ 0.03
** Display: 7’’ LVDS
** Hard drive: SATA SSD 8G
* Crown Bay
** Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
** BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
** Display = 13’’ LVDS
** Hard drive: SATA HD 160G
** wifi card: Intel wifi link 5100

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* System Use Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

Quality/1.2.0 IVI Update Test Plan

2011-10-19T03:04:17Z

Shuangeeer: /* Checkpoints */

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Checkpoints ===
Note: '''checkpoint''' in bold means it is also a sanity test point.

{|cellspacing="0" border="1"
!|Category
!|Checkpoints
|-
|System Overall
|
* [Startup] Liveboot/'''boot from local disk'''
* [Installation] Installer/Installer-shell launch and launch time
* [Installation] '''Installation in text mode and system start up(installer removal)'''
* [Installation] Installation in GUI mode and system start up(installer removal)
* [Peripherals] USB/SD auto-mounter/read/write
* [AppManager] '''Zypper install'''/update/debuginfo-install/source-install default repo configuration
* [AppManager] pkcon install/update
* [Settings] date&time settings
* [Pnp] '''Cold boot time'''
* [Pnp] Powertop log analysis, Cn state, avg resident, Wakeup times
* [Stability] Shutdown and Reboot system 10 times without failure or crash
* [Stability] Use multiple applications
|-
|Hardware Adaptation
|
* ML7213 drivers
* EG20T drivers
* '''touch screen'''
* '''Ethernet'''
* Wifi
* '''snd card'''
* onboard MMC
* '''removable MMC/USB'''
* '''USB HID'''/hub/LAN/BT dangle
* '''dmesg'''
|-
|Graphics Driver(EMGD)
|
* '''System Startup with EMGD enabled'''
* startx from console
* Switch between X/console
* '''Desktop rendering'''
* GUI installer rendering
* Check basic 3D application glxgears can be run successfully
* '''Single(LVDS) display'''
|-
|Connectivity/Communication
|
* '''Ethernet connection'''/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, '''HFP''')
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* '''gstreamer play audio/video'''
|-
|XFCE desktop
|
* '''Desktop render'''
* XFCE menu view
* '''app launch/close/switch'''
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
** CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
** BIOS: AMI 4.6.3.7/0ABXJ 0.03
** Display: 7’’ LVDS
** Hard drive: SATA SSD 8G
* Crown Bay
** Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
** BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
** Display = 13’’ LVDS
** Hard drive: SATA HD 160G
** wifi card: Intel wifi link 5100

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* System Use Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

Quality/1.2.0 IVI Update Test Plan

2011-10-19T03:02:26Z

Shuangeeer: /* Sanity Test Checkpoints */

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Checkpoints ===
{|cellspacing="0" border="1"
!|Checkpoints
!|Details
|-
|System Overall
|
* [Startup]Liveboot/'''boot from local disk'''
* [Installation]Installer/Installer-shell launch and launch time
* [Installation]'''Installation in text mode and system start up(installer removal)'''
* [Installation]Installation in GUI mode and system start up(installer removal)
* [Peripherals]USB/SD auto-mounter/read/write
* [AppManager]'''Zypper install'''/update/debuginfo-install/source-install default repo configuration
* [AppManager]pkcon install/update
* [Settings]date&time settings
* [Pnp]'''Cold boot time'''
* [Pnp]Powertop log analysis, Cn state, avg resident, Wakeup times
* [Stability]Shutdown and Reboot system 10 times without failure or crash
* [Stability]Use multiple applications
|-
|Hardware Adaptation
|
* ML7213 drivers
* EG20T drivers
* '''touch screen'''
* '''Ethernet'''
* Wifi
* '''snd card'''
* onboard MMC
* '''removable MMC/USB'''
* '''USB HID'''/hub/LAN/BT dangle
* '''dmesg'''
|-
|Graphics Driver(EMGD)
|
* '''System Startup with EMGD enabled'''
* startx from console
* Switch between X/console
* '''Desktop rendering'''
* GUI installer rendering
* Check basic 3D application glxgears can be run successfully
* '''Single(LVDS) display'''
|-
|Connectivity/Communication
|
* '''Ethernet connection'''/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, '''HFP''')
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* '''gstreamer play audio/video'''
|-
|XFCE desktop
|
* '''Desktop render'''
* XFCE menu view
* '''app launch/close/switch'''
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
** CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
** BIOS: AMI 4.6.3.7/0ABXJ 0.03
** Display: 7’’ LVDS
** Hard drive: SATA SSD 8G
* Crown Bay
** Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
** BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
** Display = 13’’ LVDS
** Hard drive: SATA HD 160G
** wifi card: Intel wifi link 5100

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* System Use Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

Quality/1.2.0 IVI Update Test Plan

2011-10-19T02:44:12Z

Shuangeeer: /* Hardware */

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Sanity Test Checkpoints ===
{|cellspacing="0" border="1"
!|Checkpoints
!|Details
|-
|Installation
|
* Installer/Installer-shell launch and launch time
* Installation in text mode and system startup(installer removal)
* Installation in GUI mode and system startup(installer removal)
|-
|System startup & shutdown
|
* Boot from local disk(X and console)
* Cold boot time and shutdown time
* Startx from console
|-
|Powertop Log
|
* Powertop log analysis, Cn state, avg resident, Wakeup times
|-
|Stability
|
* Shutdown and Reboot system 10 times without failure or crash
* Use multiple applications
|-
|XFCE desktop
|
* Desktop render
* X/console switch
* XFCE menu view
* app launch/close/switch
|-
|Connectivity -- Multi-tabs websites surfing and flash plugin check
|
* Ethernet connection/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, HFP)
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* gstreamer play audio/video
|-
|Peripheral devices
|
* Touch Screen
* USB keyboard/mouse
* USB stick/SD
|-
|Basic linux command such as Zypper install/ debuginfo-install
|
* Zypper install/update/debuginfo-install/source-install default repo configuration
* pkcon install/update
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
** CRB = Brookville + ICM(Intel® Atom™ CPU E6XX Series + LAPIS ML7213 IOH)
** BIOS: AMI 4.6.3.7/0ABXJ 0.03
** Display: 7’’ LVDS
** Hard drive: SATA SSD 8G
* Crown Bay
** Crown Bay CRB = Shell Bay Fab2(Intel® EG20T IOH) + Little Bay REV D(Intel® Atom™ CPU E6XX Series)
** BIOS: AMI 4.6.3.7, Project 0ABTN 0.20
** Display = 13’’ LVDS
** Hard drive: SATA HD 160G
** wifi card: Intel wifi link 5100

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* System Use Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

Quality/1.2.0 IVI Update Test Plan

2011-10-19T02:41:51Z

Shuangeeer: Created page with "= MeeGo 1.2.0 IVI Software Update Test Plan = == Test Objective == MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated ..."

= MeeGo 1.2.0 IVI Software Update Test Plan =

== Test Objective ==
MeeGo 1.2.0 IVI Software update testing is to validate the functionality of entire MeeGo 1.2.0 system updated distribution, to assure that
* the health of distribution built based on 1.2.0 release repo and update repo(1.2.0 update release build)
* the health of 1.2.0 release distribution after system update
* validate whether relative bugs are fixed by update patch
* explore regression issues when system is with updated software

== Feature to be Tested ==
* MeeGo 1.2.0 IVI update release(XFCE desktop, BAT drivers/middleware)
* MeeGo 1.2.0 IVI final release can be successfully upgraded to update release
* New features or bug fixings introduced by updated packages
* Functionality and reliability in resulting upgraded system function
* Performance of MeeGo 1.2.0 update release

== Test Strategy and Approach ==
=== Test Approach ===
* Install/Update system in various ways as below:
** Install 1.2.0 update release build directly to get latest software stuff
** system Upgrade from 1.2.0 final release
* Validate the system with below criteria:
** Software update can be previewed and easily completed via command line (zypper, pkcon).
** New functions of latest build works
** Unchanged functions are not broken
** No regression on performance and reliability of whole system

=== Test Cycle ===
* Sanity Testing
** Generally, update repo will be delivered each 1-2 weeks based on bug fix progress;
** QA will do sanity testing when new update repo/build is ready and cover:
*** XFCE sanity testing
*** Middleware components sanity testing
*** IVI drivers sanity testing
*** Bug verification and regression testing
* System Function Testing
** QA will conduct one round of system function testing to evaluate whole update system quality for update release final repo

== Test Design ==
=== Sanity Test Checkpoints ===
{|cellspacing="0" border="1"
!|Checkpoints
!|Details
|-
|Installation
|
* Installer/Installer-shell launch and launch time
* Installation in text mode and system startup(installer removal)
* Installation in GUI mode and system startup(installer removal)
|-
|System startup & shutdown
|
* Boot from local disk(X and console)
* Cold boot time and shutdown time
* Startx from console
|-
|Powertop Log
|
* Powertop log analysis, Cn state, avg resident, Wakeup times
|-
|Stability
|
* Shutdown and Reboot system 10 times without failure or crash
* Use multiple applications
|-
|XFCE desktop
|
* Desktop render
* X/console switch
* XFCE menu view
* app launch/close/switch
|-
|Connectivity -- Multi-tabs websites surfing and flash plugin check
|
* Ethernet connection/disconnection/file transfer(proxy)
* Wifi scan/connection/disconnection
* Bluetooth pairing/connection(A2DP, HFP)
|-
|Multimedia
|
* aplay/arecord
* paplay/parec
* gstreamer play audio/video
|-
|Peripheral devices
|
* Touch Screen
* USB keyboard/mouse
* USB stick/SD
|-
|Basic linux command such as Zypper install/ debuginfo-install
|
* Zypper install/update/debuginfo-install/source-install default repo configuration
* pkcon install/update
|-
|}

== Test Environment ==
=== Hardware ===
* Crossville/Lapis
* Crown Bay

=== Test Repos ===
* MeeGo 1.2.0 Release Repo
** http://repo.meego.com/MeeGo/releases/1.2.0/
* MeeGo 1.2.0 Update Repo
** Formal Repo:
*** http://repo.meego.com/MeeGo/updates/1.2.0/
** Test Repo:
*** http://repo.meego.com/MeeGo/builds/1.2.0/latest/

== QA Contact ==
* [mailto:yanshuang.zheng@intel.com Zheng Yanshuang]

== Test Report ==
* Sanity Test Report
** http://qa-reports.meego.com/1.2/IVI/Sanity/
* System Use Test Report
** http://qa-reports.meego.com/1.2/IVI/Milestone/

== Referrences ==
* Software Update Process: http://wiki.meego.com/Release_Engineering/Software_update_process

Quality

2011-10-19T00:48:49Z

Shuangeeer: /* Projects */

= Quality =

This page is for MeeGo Quality Assurance related material.

== Getting Started ==
* [[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]]
|
* [[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]]
|
* [[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]
|
* [[Quality/1.2.0_IVI_Update_Test_Plan|1.2.0 Update 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|Find our tools and contact information]]
* [[Quality/QA tools development|Participate in development activities]]. You are most welcome!

The following links provide some basic information on QA tools and their usage.
* [[Quality/QA-tools/How_to_set_up_repositories|Setting up the repositories for installing tools]] (please note that not all tools are in these repositories yet)
* [[Quality/QA-tools/Test packaging|Test packaging]]: Test packaging is the mechanism to wrap any tests in rpm packages to automate execution.
* [[Quality/QA-tools/Autotest-guide|Autotest-Guide]]: A guide for setting up automated testing environment. It includes instructions how to automate test execution and image installations.

== Procedures and best practices ==

* [[Quality/Plans/Testability-checklist|Feature Testability Checklist]]
** The basic intent of the feature review is to make sure that all features/requirements defined for MeeGo release are '''testable'''. The target is to map test cases in Distro testing against requirements, so we can determine whether features are '''done'''. This checklist / guideline should be used when reviewing MeeGo's features. Review comments will be given based on this checklist.
* [[Quality/Testability-commenting|Testability Commenting Guide]]
** This is a guide for QA contacts about how to comment on feature testability so as to provide as much information as possible to test developers.
*[[Quality/TestSuite/MCTS/MCTS_Development_Guideline | MeeGo Core Test Suites Development Guidelines]] 
*[[MeeGo Core Test Suites Packaging draft]] 
* [[Quality/Plans/Test-plan-template|Test plan template]] -- PROPOSAL, please contribute
* [[CompTestPlanTemplate|Component Test Plan Template]] -- WORK IN PROGRESS, please contribute
* [[Quality/Test_case_template|Test Case Template]] -- Updated, ready for approval
* [[Quality/TestDesignProcessAndGuideline| Test Design Process and Guideline]] -- WORK IN PROGRESS, please contribute
* [[Quality/TestSetGuideline| Test Set Guideline]]
* [[Quality/Test management overview|Test management overview]]

== Defect tracking ==

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

== 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.

== Tasks of the "QA Contact" ==

* QA contact work with/support/advice/help package maintainers (see [http://fedoraproject.org/wiki/PackageMaintainers/MaintainerResponsibility|Fedora example] or [[Packaging/Guidelines#Maintaining_a_Package|MeeGo guidelines for maintaining 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 [[Quality/Bug_Life_Cycle_and_Handling|Bug Life Cycle and Handling page]])
*** 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/CoreQualityMetrics

2011-08-01T09:41:39Z

Shuangeeer: /* Key Messages */

=== Key Messages ===
* Highlight
** 41 FIXED bugs have been verified during last week. There are now 65 bugs tagged "Verification-pending".

* Lowlight(Bug follow up)
** There are 217 bugs in status NEW, while 191(92.4%->88%) of them were filed 2 weeks ago. Hope owners could review and accept bugs in time.

* Regular activities
** 42(28->31->42) core bugs were NEW filed last week, while 32(41->29->32) bugs were FIXED.
** Currently there are 374(361->375->374) core 1.2 open bugs, including 59(65->62->59) high bugs.
** 51 bugs were triaged last week.

=== MeeGo 1.2 - Core Release Blockers ===
* '''Open Release Blockers'''
** See all proposed release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_release_blocker_proposed&sharer_id=234 here]
** See all approved release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_release_blocker_approved&sharer_id=234 here]

* '''Open Update Release Blockers'''
** See all proposed update release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_update_release_blocker_proposed&sharer_id=234 here]
** See all approved update release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_update_release_blocker_approved&sharer_id=234 here]

''Table. Blockers in numbers'' 
{| border="1"
!
! MeeGo Release Blocker
! MeeGo Update Release Blockers
|-
|Approved
|24(25->24)
|3(4->3)
|-
|Proposed
|16(10->16)
|9(11->9)
|} 

=== MeeGo 1.2 - Core Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.2 Core Open bugs by priority.
** ''[2011-08-01]'' 374(361->375->374) Bugs are open, including 59(65->62->59) High bugs, 234(209->227->234) Medium Bugs.

''Figure. Open Bugs / Priority'' 
[[File:1.2_open_bug_priority.png]] 

* ''' Open Bugs / Components in numbers'''
{{#bugzilla:
|group=component
|grouporder=asc
|bar=priority
|product=OS Base,OS Middleware
|version=1.2
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
}}
 
* '''FNV Bugs / Resolutions in numbers'''
** [2011-07-18] RELEASED/FIXED: 181; RESOLVED/FIXED: 32
** [2011-07-25] RELEASED/FIXED: 89; RESOLVED/FIXED: 37
** [2011-08-01] RELEASED/FIXED: 88; RESOLVED/FIXED: 29
{{#bugzilla:
|group=status
|grouporder=asc
|bar=resolution
|product=OS Base,OS Middleware
|version=1.2
|status=RESOLVED,RELEASED
}}
 
* '''Accumulated bugs'''
** [2011-07-18] Total: 1937 with 1269 VERIFIED/CLOSED.
** [2011-07-25] Total: 1948 with 1355 VERIFIED/CLOSED.
** [2011-08-01] Total: 1969 with 1427 VERIFIED/CLOSED.
{{#bugzilla:
|group=product
|grouporder=asc
|bar=status
|product=OS Base,OS Middleware
|version=1.2
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED,RESOLVED,RELEASED,VERIFIED,CLOSED
}}
 

* '''Top/Hot issues(2011-07-25)'''
{{#bugzilla:
|columns=id,priority,status,resolution,summary
|product=OS Base,OS Middleware
|version=1.2
|group=component
|id=21243,9205,20852,21286,21440,20276
|sort=component,priority,id
}}

=== MeeGo 1.3 - Core Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.3 Core Open bugs by priority.

''Figure. Open Bugs / Priority'' 
[[File:1.3_open_bug_priority.png]] 

* '''Top 5 Components'''
''Table. Bugs / Components in numbers'' 
{| border="1"
! Component
! 2011-06-27
|-
|Virtual Keyboard
|15
|-
|Connection manager
|13(4->13)
|-
|Package management
|7(6->7)
|-
|Graphics subsystem
|6(3->6)
|-
|Installation
|5
|} 

* '''Top/Hot issues'''
{{#bugzilla:
|columns=id,priority,status,resolution,summary
|product=OS Base,OS Middleware
|version=1.3
|group=component
|id=19251,20216,19052,19839,20179,20126,20461,17393,19386,19770
|sort=component,priority,id
}}

* '''Accumulated bugs / week'''
** This graph shows the 1.3 Core accumulated bugs by status per week.
[[File:1.3_bug_accumulates.png]] 

* '''Accumulated bugs'''
{{#bugzilla:
|group=product
|grouporder=asc
|bar=status
|product=OS Base,OS Middleware
|version=1.3
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED,RESOLVED,RELEASED,VERIFIED,CLOSED
}}

=== MeeGo 1.2&1.3 - Core Bug Activities ===
* '''New bugs / week'''
** This graph shows how many Core bugs are newly reported or fixed per week

''Figure. New/Fixed bugs / week'' 
[[File:new_fixed_bugs_week.jpg]] 

** '''Top Fixed bugs / Assignee'''
''Table. Bugs / Components in numbers'' 
{| border="1"
! Assignee
! From 07-11 to 07-18
|-
|guillaume.zajac@intel.com || 4 (ConnMan/1.3)
|-
|vivian.zhang@intel.com || 4 (Media subsystem)
|-
|bintian.wang@windriver.com || 3 (Sensor Framework)
|-
|mengdong.lin@intel.com || 3 (audio/bluetooth)
|-
|} 

=== MeeGo 1.2&1.3 - Core Bug Inactivities ===

* '''191(198->195->191) Bugs with Status = NEW for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_New_2weeks&sharer_id=234 here] (''Expected to be accepted by assignee soon by changing status to ASSIGNED'')

* '''38(18->17->38) HIGH open bugs without update >= 1 month''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_High_NoUpdate_1Month&sharer_id=234 here](''Expected to be FIXED in 2 weeks'')

* '''30(24->28->30) Bugs with Status = RESOLVED/FIXED for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Resolved_2weeks&sharer_id=234 here](''Expected to be RELEASED soon thus QA could verify them'')

* '''77(134->78->77) Bugs with Status = RELEASED/FIXED for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Released_2weeks&sharer_id=234 here](''Expected to be VERIFIED soon'')

=== MeeGo 1.2&1.3 - Core WONTFIX Bugs ===
Click [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Wontfix&sharer_id=234 here] to see all wontfix bugs of MeeGo Core

Quality/CoreQualityMetrics

2011-08-01T09:32:59Z

Shuangeeer: /* MeeGo 1.2&1.3 - Core Bug Inactivities */

=== Key Messages ===
* Highlight
** 41 FIXED bugs have been verified during last week. There are now 65 bugs tagged "Verification-pending".

* Lowlight(Bug follow up)
** There are 217 bugs in status NEW, while 191(92.4%->88%) of them were filed 2 weeks ago. Hope owners could review and accept bugs in time.

* Regular activities
** 42(28->31->42) core bugs were NEW filed last week, while 32(41->29->32) bugs were FIXED.
** Currently there are 375(388->361->375) core 1.2 open bugs, including 62(73->65->62) high bugs.
** 51 bugs were triaged last week.

=== MeeGo 1.2 - Core Release Blockers ===
* '''Open Release Blockers'''
** See all proposed release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_release_blocker_proposed&sharer_id=234 here]
** See all approved release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_release_blocker_approved&sharer_id=234 here]

* '''Open Update Release Blockers'''
** See all proposed update release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_update_release_blocker_proposed&sharer_id=234 here]
** See all approved update release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_update_release_blocker_approved&sharer_id=234 here]

''Table. Blockers in numbers'' 
{| border="1"
!
! MeeGo Release Blocker
! MeeGo Update Release Blockers
|-
|Approved
|24(25->24)
|3(4->3)
|-
|Proposed
|16(10->16)
|9(11->9)
|} 

=== MeeGo 1.2 - Core Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.2 Core Open bugs by priority.
** ''[2011-08-01]'' 374(361->375->374) Bugs are open, including 59(65->62->59) High bugs, 234(209->227->234) Medium Bugs.

''Figure. Open Bugs / Priority'' 
[[File:1.2_open_bug_priority.png]] 

* ''' Open Bugs / Components in numbers'''
{{#bugzilla:
|group=component
|grouporder=asc
|bar=priority
|product=OS Base,OS Middleware
|version=1.2
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
}}
 
* '''FNV Bugs / Resolutions in numbers'''
** [2011-07-18] RELEASED/FIXED: 181; RESOLVED/FIXED: 32
** [2011-07-25] RELEASED/FIXED: 89; RESOLVED/FIXED: 37
** [2011-08-01] RELEASED/FIXED: 88; RESOLVED/FIXED: 29
{{#bugzilla:
|group=status
|grouporder=asc
|bar=resolution
|product=OS Base,OS Middleware
|version=1.2
|status=RESOLVED,RELEASED
}}
 
* '''Accumulated bugs'''
** [2011-07-18] Total: 1937 with 1269 VERIFIED/CLOSED.
** [2011-07-25] Total: 1948 with 1355 VERIFIED/CLOSED.
** [2011-08-01] Total: 1969 with 1427 VERIFIED/CLOSED.
{{#bugzilla:
|group=product
|grouporder=asc
|bar=status
|product=OS Base,OS Middleware
|version=1.2
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED,RESOLVED,RELEASED,VERIFIED,CLOSED
}}
 

* '''Top/Hot issues(2011-07-25)'''
{{#bugzilla:
|columns=id,priority,status,resolution,summary
|product=OS Base,OS Middleware
|version=1.2
|group=component
|id=21243,9205,20852,21286,21440,20276
|sort=component,priority,id
}}

=== MeeGo 1.3 - Core Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.3 Core Open bugs by priority.

''Figure. Open Bugs / Priority'' 
[[File:1.3_open_bug_priority.png]] 

* '''Top 5 Components'''
''Table. Bugs / Components in numbers'' 
{| border="1"
! Component
! 2011-06-27
|-
|Virtual Keyboard
|15
|-
|Connection manager
|13(4->13)
|-
|Package management
|7(6->7)
|-
|Graphics subsystem
|6(3->6)
|-
|Installation
|5
|} 

* '''Top/Hot issues'''
{{#bugzilla:
|columns=id,priority,status,resolution,summary
|product=OS Base,OS Middleware
|version=1.3
|group=component
|id=19251,20216,19052,19839,20179,20126,20461,17393,19386,19770
|sort=component,priority,id
}}

* '''Accumulated bugs / week'''
** This graph shows the 1.3 Core accumulated bugs by status per week.
[[File:1.3_bug_accumulates.png]] 

* '''Accumulated bugs'''
{{#bugzilla:
|group=product
|grouporder=asc
|bar=status
|product=OS Base,OS Middleware
|version=1.3
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED,RESOLVED,RELEASED,VERIFIED,CLOSED
}}

=== MeeGo 1.2&1.3 - Core Bug Activities ===
* '''New bugs / week'''
** This graph shows how many Core bugs are newly reported or fixed per week

''Figure. New/Fixed bugs / week'' 
[[File:new_fixed_bugs_week.jpg]] 

** '''Top Fixed bugs / Assignee'''
''Table. Bugs / Components in numbers'' 
{| border="1"
! Assignee
! From 07-11 to 07-18
|-
|guillaume.zajac@intel.com || 4 (ConnMan/1.3)
|-
|vivian.zhang@intel.com || 4 (Media subsystem)
|-
|bintian.wang@windriver.com || 3 (Sensor Framework)
|-
|mengdong.lin@intel.com || 3 (audio/bluetooth)
|-
|} 

=== MeeGo 1.2&1.3 - Core Bug Inactivities ===

* '''191(198->195->191) Bugs with Status = NEW for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_New_2weeks&sharer_id=234 here] (''Expected to be accepted by assignee soon by changing status to ASSIGNED'')

* '''38(18->17->38) HIGH open bugs without update >= 1 month''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_High_NoUpdate_1Month&sharer_id=234 here](''Expected to be FIXED in 2 weeks'')

* '''30(24->28->30) Bugs with Status = RESOLVED/FIXED for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Resolved_2weeks&sharer_id=234 here](''Expected to be RELEASED soon thus QA could verify them'')

* '''77(134->78->77) Bugs with Status = RELEASED/FIXED for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Released_2weeks&sharer_id=234 here](''Expected to be VERIFIED soon'')

=== MeeGo 1.2&1.3 - Core WONTFIX Bugs ===
Click [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Wontfix&sharer_id=234 here] to see all wontfix bugs of MeeGo Core

File:New fixed bugs week.jpg

2011-08-01T09:31:26Z

Shuangeeer: uploaded a new version of "File:New fixed bugs week.jpg"

2011-07-25T09:25:01Z

Shuangeeer: /* Key Messages */

=== Key Messages ===
* Highlight
** 86 FIXED bugs have been verified during last week, with extra 6 bugs tagged "Verification-pending".

* Lowlight(Bug follow up)
** There are 211 bugs in status NEW, while 195(92.4%) of them were filed 2 weeks ago. Hope owners could review and accept bugs in time.
** 78 Bugs with Status = RELEASED/FIXED for >=2 weeks(37 of them tagged "Verification-pending"). The rest bugs need QA continue on verification: https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Released_2weeks&sharer_id=234

* Regular activities
** 31(36->28->31) core bugs were NEW filed last week, while 29(30->41->29) bugs were FIXED.
** Currently there are 375(388->361->375) core 1.2 open bugs, including 62(73->65->62) high bugs.
** 46 bugs were triaged last week.

=== MeeGo 1.2 - Core Release Blockers ===
* '''Open Release Blockers'''
** See all proposed release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_release_blocker_proposed&sharer_id=234 here]
** See all approved release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_release_blocker_approved&sharer_id=234 here]

* '''Open Update Release Blockers'''
** See all proposed update release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_update_release_blocker_proposed&sharer_id=234 here]
** See all approved update release blockers: [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_1.2_open_update_release_blocker_approved&sharer_id=234 here]

''Table. Blockers in numbers'' 
{| border="1"
!
! MeeGo Release Blocker
! MeeGo Update Release Blockers
|-
|Approved
|24(25->24)
|3(4->3)
|-
|Proposed
|16(10->16)
|9(11->9)
|} 

=== MeeGo 1.2 - Core Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.2 Core Open bugs by priority.
** ''[2011-07-25]'' 375(388->361->375) Bugs are open, including 62(73->65->62) High bugs, 227(211->209->227) Medium Bugs.

''Figure. Open Bugs / Priority'' 
[[File:1.2_open_bug_priority.png]] 

* ''' Open Bugs / Components in numbers'''
{{#bugzilla:
|group=component
|grouporder=asc
|bar=priority
|product=OS Base,OS Middleware
|version=1.2
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED
}}
 
* '''FNV Bugs / Resolutions in numbers'''
** [2011-07-18] RELEASED/FIXED: 181; RESOLVED/FIXED: 32
** [2011-07-25] RELEASED/FIXED: 89; RESOLVED/FIXED: 37
{{#bugzilla:
|group=status
|grouporder=asc
|bar=resolution
|product=OS Base,OS Middleware
|version=1.2
|status=RESOLVED,RELEASED
}}
 
* '''Accumulated bugs'''
** [2011-07-18] Total: 1937 with 1269 VERIFIED/CLOSED.
** [2011-07-25] Total: 1948 with 1355 VERIFIED/CLOSED.
{{#bugzilla:
|group=product
|grouporder=asc
|bar=status
|product=OS Base,OS Middleware
|version=1.2
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED,RESOLVED,RELEASED,VERIFIED,CLOSED
}}
 

* '''Top/Hot issues(2011-07-04)'''
{{#bugzilla:
|columns=id,priority,status,resolution,summary
|product=OS Base,OS Middleware
|version=1.2
|group=component
|id=21170,16997,21157,21190,21131,21286
|sort=component,priority,id
}}

=== MeeGo 1.3 - Core Bugs Status ===

* '''Open Bugs / Priority'''
** This graph shows the current status of the 1.3 Core Open bugs by priority.

''Figure. Open Bugs / Priority'' 
[[File:1.3_open_bug_priority.png]] 

* '''Top 5 Components'''
''Table. Bugs / Components in numbers'' 
{| border="1"
! Component
! 2011-06-27
|-
|Virtual Keyboard
|15
|-
|Connection manager
|13(4->13)
|-
|Package management
|7(6->7)
|-
|Graphics subsystem
|6(3->6)
|-
|Installation
|5
|} 

* '''Top/Hot issues'''
{{#bugzilla:
|columns=id,priority,status,resolution,summary
|product=OS Base,OS Middleware
|version=1.3
|group=component
|id=19251,20216,19052,19839,20179,20126,20461,17393,19386,19770
|sort=component,priority,id
}}

* '''Accumulated bugs / week'''
** This graph shows the 1.3 Core accumulated bugs by status per week.
[[File:1.3_bug_accumulates.png]] 

* '''Accumulated bugs'''
{{#bugzilla:
|group=product
|grouporder=asc
|bar=status
|product=OS Base,OS Middleware
|version=1.3
|status=NEW,NEEDINFO,ASSIGNED,WAITING FOR UPSTREAM,REOPENED,RESOLVED,RELEASED,VERIFIED,CLOSED
}}

=== MeeGo 1.2&1.3 - Core Bug Activities ===
* '''New bugs / week'''
** This graph shows how many Core bugs are newly reported or fixed per week

''Figure. New/Fixed bugs / week'' 
[[File:new_fixed_bugs_week.jpg]] 

** '''Top Fixed bugs / Assignee'''
''Table. Bugs / Components in numbers'' 
{| border="1"
! Assignee
! From 07-11 to 07-18
|-
|guillaume.zajac@intel.com || 4 (ConnMan/1.3)
|-
|vivian.zhang@intel.com || 4 (Media subsystem)
|-
|bintian.wang@windriver.com || 3 (Sensor Framework)
|-
|mengdong.lin@intel.com || 3 (audio/bluetooth)
|-
|} 

=== MeeGo 1.2&1.3 - Core Bug Inactivities ===

* '''195(221->215->198->195) Bugs with Status = NEW for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_New_2weeks&sharer_id=234 here] (''Expected to be accepted by assignee soon by changing status to ASSIGNED'')

* '''17(11->23->18->17) HIGH open bugs without update >= 1 month''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_High_NoUpdate_1Month&sharer_id=234 here](''Expected to be FIXED in 2 weeks'')

* '''28(50->36->24->28) Bugs with Status = RESOLVED/FIXED for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Resolved_2weeks&sharer_id=234 here](''Expected to be RELEASED soon thus QA could verify them'')

* '''78(174->134->134->78) Bugs with Status = RELEASED/FIXED for >=2 weeks''': [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Keep_Released_2weeks&sharer_id=234 here](''Expected to be VERIFIED soon'')

=== MeeGo 1.2&1.3 - Core WONTFIX Bugs ===
Click [https://bugs.meego.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Core_Wontfix&sharer_id=234 here] to see all wontfix bugs of MeeGo Core

File:New fixed bugs week.jpg

2011-07-25T09:19:04Z

Shuangeeer: uploaded a new version of "File:New fixed bugs week.jpg"

2011-07-20T07:37:45Z

Shuangeeer: /* Installation */

== Release Status ==

* '''1.2.0.1:'''
**　'''First update of 1.2.0 has been released on 2011-07-15. See details at https://meego.com/downloads/releases/updates/meego-v1.2.0.1-ivi-update '''


== Bug List ==

{| border="1"
! LEGEND
! Comment
|-
| style="background: #33CC33"| || SRs completed, QA verified
|-
| style="background: #ee2222"| || Patch ready but still need SRs(accepted) and QA's verification
|}

=== Generic ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17502 || NEW || || U+ || 18913 || NEW || || [IVI] boot time is too long ~35 seconds ||
|}

=== Graphics ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: gray"
| 14641 || VERIFIED || WONTFIX || U? || 18976 || VERIFIED || WONTFIX || [IVI] Dual Head display support for Russellville/Northville ||
|-
| 16929 || NEW || || U? || 18978 || NEW || || IVI/Russellville: hang when switch from command line to X ||
|-
| 17177 || NEW || || U? || 18979 || NEW || ||[IVI]tear/black screen showed sometimes on LVDS'13 || Still reproduced with emgd-bin-2027
|- style="background: #33cc33"
| 17851 || RELEASED || FIXED || U+ || 18919 || RESOLVED || FIXED ||[IVI] EMGD returns 24-bit XRGB visual when a 32-bit ARGB visual is needed for EGL support of QT|| RELEASED in 1.2.0.1 on 2011-07-15
|- style="background: #33cc33"
| 18707 || VERIFIED || FIXED || U+ || 18918 || RELEASED || FIXED || [IVI] EMGD-bin: meego-ux-daemon crashes QT at various times (lock screen, task switcher, when idle) || RELEASED in 1.2.0.1 on 2011-07-15[Workaround for BMC# 16997]
|- style="background: #33cc33"
| 19087 || VERIFIED || FIXED || U+ || 20194 || RESOLVED || FIXED || [IVI] X init failed if emgd update to 2001-4|| RELEASED in 1.2.0.1 on 2011-07-15
|- style="background: #33cc33"
| 19386 || VERIFIED || FIXED || U+ || 20195 || RESOLVED || FIXED || [IVI][REG] Lock screen not rendered on top of IVI desktop with emgd-bin-2001-4 || RELEASED in 1.2.0.1 on 2011-07-15
|- style="background: #33cc33"
| || || || || 19377 || VERIFIED || FIXED || [IVI][REG] App switcher show black frame for launched app icons with emgd-2001 || RELEASED in 1.2.0.1 on 2011-07-15
|}

=== Installation ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: #33cc33"
| 11781 || RELEASED || FIXED || U+ || 18915 || RESOLVED || FIXED || [IVI] Failed to install the meego ivi with text installation when the hdd is new brand || RELEASED in 1.2.0.1 on 2011-07-15 Need verification by bug reporter. 
|-
| 15443 || NEW || || U+ || 18916 || NEW || || GUI Installer hangs when a storage device partition table cannot be read ||
|-
| 16876 || NEW || || U+ || 18917 || NEW || || [IVI] RV: GUI Installer takes a long time to launch ||
|}

=== Kernel&Drivers ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|- style="background: #33cc33"
| 17135 || RELEASED || FIXED || U+ || 18981 || RELEASED || FIXED || CrossvilleOKI: ioh_video_in initialize failed || RELEASED in Update 1.2.0.1 on 2011-07-15. Pending verification using new boards.
|-
| 17467 || NEW || || U? || 18982 || NEW || || IVI/Crossville-OKI: touchscreen NOT function ||
|- style="background: #33CC33"
| 18980 || VERIFIED || FIXED || U+ || 15611 || RELEASED || FIXED || Wrong driver is loading on Crown Bay's EG20T serial port ( same will occur on ML7213) || RELEASED in Update 1.2.0.1 on 2011-07-15
|- style="background: #33CC33"
| 18988 || VERIFIED || FIXED || U+ || 17042 || RELEASED || FIXED || Turn off expensive debug config options for release || RELEASED in Update 1.2.0.1 on 2011-07-15
|- style="background: #33CC33"
| 18991 || VERIFIED || FIXED || U+ || 17774 || RELEASED || FIXED || xen missing from kernel-adaptation-intel-automotive-devel || RELEASED in Update 1.2.0.1 on 2011-07-15
|- style="background: #33CC33"
| 16760 || VERIFIED || FIXED || U+ || 18977 || RELEASED || FIXED || [IVI] Russellville: /dev/radio0 not found || RELEASED in Update 1.2.0.1 on 2011-07-15
|- style="background: #33cc33"
| 20501 || VERIFIED || FIXED || U+ || 20500 || RELEASED || FIXED || Apply various critical driver patches from vendor for Crossville/OKI-ML7213 || RELEASED in Update 1.2.0.1 on 2011-07-15
|} 

=== meego-ux-ivi ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| 17391 || REOPENED || || U? || 18985 || NEW || || [IVI]screen lock function will kill running app ||
|- style="background: #33CC33"
| 18987 || VERIFIED || FIXED || U+ || 16941 || RELEASED || FIXED || [IVI] no prompt give out when open deleted apps on desktop menu || Available in 1.2.0.0.1.20110629.1
|- style="background: #33CC33"
| 18989 || VERIFIED || FIXED || U+ || 17184 || RELEASED || FIXED || [VoiceCommand] failed to launch task menu by "Tasks" || Available in 1.2.0.0.1.20110629.1
|- style="background: #33CC33"
| 18990 || VERIFIED || FIXED || U+ || 17438 || RELEASED || FIXED || [IVI][VoiceCommand] failed to open apps directly || Available in 1.2.0.0.1.20110629.1
|- style="background: #33cc33"
| 17393 || VERIFIED || FIXED || U+ || 20198 || NEW || || [IVI] screen should not lock when navigating || Accepted SR#22034 into 1.2.0:Update. No SR into 1.2 branch. QA verified
|- style="background: #33cc33"
| 19052 || VERIFIED || FIXED || U+ || 20200 || NEW || || [IVI]: IVI UX should be visible at all times by default || Accepted SR#22034 into 1.2.0:Update. No SR into 1.2 branch. QA verified
|} 

=== Qt&QtContacts ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
|18845 || NEW || || U+ || 18914 || NEW || || [IVI] Qt EGL graphics selects wrong "visual id" for secondary screen and crashes ||
|-
|18986 || NEW || || U? || 16997 || REOPENED || || meego-ux-daemon crashes QT at various times (lock screen, task switcher, when idle) || Workaround BMC#18707
|-
|18983 || NEW || || U? || 15948 || REOPENED || || [REG]Fail to run ut_qtcontacts_trackerplugin || qtcontacts-tracker is going to be replaced with qtcontacts-eds
|} 

=== Other Candidates ===
{| border="1"
! ID(1.2.0)
! Status
! Resolution
! Flag
! ID(1.2)
! Status
! Resolution
! Summary
! Comment
|-
| || || || || 17460 || NEW || || [IVI][REG] screen flickers when hovering cursors on the active buttons/text input box of Manage Apps ||
|-
| || || || R+, U+ || 19764 || NEEDINFO || || kernel-adaptation-intel-automotive source RPM fails to build ||
|-
| || || || R+, U+ || 10420 || NEW || || Failed to switch between X and console after kernel updated ||
|- style="background: #ee2222"
| 20276 || NEW || || U+ || 19353 || RELEASED || FIXED || Tracker fail to find the media files from USB disk. || No SR into 1.2.0 update. SR accepted into 1.2 branch.
|}