MeeGo Quality Approach

Session Summary:

MeeGo is an open source Linux software stack targeted to support multiple devices, Netbook, Handset, In-Vehicle, Connected TV, with MeeGo Core shared across all the devices. How to ensure MeeGo Quality on all the different vertical User Experience and MeeGo Core stack? Nokia and Intel QA have worked together to establish MeeGo QA approaches and process, which includes test plan for MeeGo Core and Vertical UX, test set guideline, test cycle and test process for MeeGo code line, quality target for MeeGo milestone, QA reporting, QA tools for test case management, test case automation and test process automation, and MeeGo bug triage process. The goal of this session is to provide an overall for MeeGo Quality Assurance, and open the opportunity for community to involve in MeeGo QA process and contribute to MeeGo quality activities.

Session Abstract:

This session will present MeeGo Quality Approaches established to drive MeeGo quality by Intel and Nokia QA.

1. Test Approach for MeeGo. MeeGo has been tested through different layers, MeeGo UX for different verticals, MeeGo Core and MeeGo Base OS.

2. Test Set Guideline and Test Cycle. MeeGo has sanity test, feature test, System Test (functional, performance and reliablity), regression test etc. MeeGo test cycle includes hourly, daily, weekly and milestone test cycle with different objectives for each. Hourly testing is fully automated testing bulit on top of Open Test System for trunk:testing, with objective to report major regressions at the early time, the hourly test result is referred by MeeGo distribution release engineer and architect to decide package promotion from trunk:testing to trunk. daily sanity testing is performed for trunk to report out the basic health of MeeGo distribution everyday, weekly testing is performed for preview image and weekly release image to ensure weekly release quality. By definition, milestone test cycle is aligned with MeeGo milestone (FC, RC, PR) to ensure milestone target to be achieved through proper QA testing.

3. Test Process for MeeGo code line from MeeGo stage, trunk:testing to trunk

4. Quality Target for MeeGo Milestone. MeeGo includes DP, FC, RC and PR milestone with different quality target for each. For example, DP is completed with intrusive changes, sanity and basic feature set will be run to ensure quality goal is achieved for DP milestone.

5. QA tools. MeeGo test asset is managed in testlink which is open source test case management tool with customzation to support MeeGo test case format. Testablity driver is used to auomate MeeGo QT based UX test automation. Open Test System (OTS) is the fully automated test sysytem for MeeGo testing and so on.

6. QA reporting. MeeGo test reports are published on MeeGo mailing list and archived on wiki.meego.com/Quality. Detail test result for test cases are available in testlink.

7. MeeGo bug triage Process. MeeGo bugs are tracked in bugs.meego.com. MeeGo bug triage is a process to dispose MeeGo bugs. There are a few MeeGo triage teams have been established, including MeeGo Core Bug Triage, MeeGo Handset UX bug triage, MeeGo Netbook UX bug triage, MeeGo i18n and L10n bug triage team etc. MeeGo new bugs usually triaged by MeeGo triage team twice a week or daily after reaching Feature complete. MeeGo triage team meet on MeeGo IRC to sync up status and discuss controversial bugs.

The MeeGo Quality approaches have been practiced for a couple of months by MeeGo QA team from Nokia and Intel in open source. We are extremely interested in working with community QA/testers to continuously improve MeeGo QA process.

Program

Sessions Details

Status: Accepted

Duration: 40 mins

Slides:
dublin_meego_qa_approach_-_final.pdf

Session Presenters

V-PV

May

The conference organizing committee has put together slide templates for presenters to use if they so choose. Feel free to take and modify as you like!