Revision as of 08:33, 26 August 2010

MeeGo SDK Test Plan (Content not ready)

Scope of this Document

This is overall test plan for MeeGo SDK(Software Development Kit) of MeeGo open source project, which defines test scope, test strategy, test configurations as well as test execution cycle for MeeGo SDK. It will give readers an overview of validation activities for MeeGo SDK 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 SDK. It will be the joint effort from Nokia, Intel and MeeGo community.

Features to Be Tested

Overall the MeeGo Core Testing will cover below host, target and testpoints:

• P1: Test focus with main functionality, make sure common case work
• P2: Nice to have for coming release
• TBD: not covered in coming release

Tools to set up develop environment

Test Host & Target

Check Pointer

What will not Be Tested

Following feature category won't be covered in MeeGo SDK testing.

• Only light test for SDK image, not check all of the functionalities or applications inside it, but only major deamon and service inside it.
• Not test for SDK package or image building, only check the built out package or images.
• Not cover Meego compliance test, but only check key package versions which should align with Meego release.
• ARM support are not tracked in this document yet, which should be owned by Nokia.
• MADDE, QT Creator will be fully tested by Nokia, no thorough test covered in this document.

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 MeeGo Quality page, and the code in 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.

Test Cycle

MeeGo Core will be tested from the following different test execution levels.

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 SDK Test Report (Bug verification, new feature exploration...)
  • Distribution Milestone Full Pass Test report
• Archive reports at MeeGo SDK Quality wiki

Environmental Needs

Hardware Platforms

MeeGo v1.1

• Aava Koski
• MRST CDK
• Medfield CDK
• N900
• Netbook

Peripherals required

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