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.
Overall the MeeGo Core Testing will cover below host, target and testpoints:
|Simulator: Xephyr + chroot||P2|
|SDK installer works||P1|
|SDK images compliance with Meego images||P1|
|Boot SDK images with Qemu||P1|
|Boot SDK images with Xephyr||P2|
|Basic function check for SDK image||need more detail checklist here||P1|
|Documents & Toturials||need detail checklist here||P1|
Following feature category won't be covered in MeeGo SDK testing.
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:
MeeGo Core will be tested from the following different test execution levels.
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.
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:
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:
|USB devices||keyboard, mouse, USB storage device , ...|
The networking arrangements needed to conduct the testing: