(→Virtual Keyboard Test Plan (In Editing)) |
(categorise, cut topevel heading, wikify table formatting) |
||
| (3 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | |||
==Component Summary== | ==Component Summary== | ||
This test plan is for MeeGo 1.1 HandSet UX Virtual keyboard (VKB). | This test plan is for MeeGo 1.1 HandSet UX Virtual keyboard (VKB). | ||
| - | The goal of Virtual Keyboard is to support key input for handset | + | The goal of Virtual Keyboard is to support multi language key input for different handset applications. |
==Feature to be Tested== | ==Feature to be Tested== | ||
All testable features coming to MeeGo 1.1 HandSet UX virtual keyboard will be covered in this test plan. | All testable features coming to MeeGo 1.1 HandSet UX virtual keyboard will be covered in this test plan. | ||
| - | + | {| class="wikitable" | |
| - | + | |+ VKB features to be tested | |
| - | {| | + | |
!| Feature Name | !| Feature Name | ||
!| Description | !| Description | ||
| Line 22: | Line 20: | ||
==Feature not to be Tested== | ==Feature not to be Tested== | ||
| - | + | there aren't features not to be tested | |
| - | + | ||
| - | + | ||
==Test Strategy and Approach== | ==Test Strategy and Approach== | ||
In general, the Virtual Keyboard test applies Black-Box test methods and refers to feature implementations to guide test design. Virtual keyboard application will be tested from different levels below: | In general, the Virtual Keyboard test applies Black-Box test methods and refers to feature implementations to guide test design. Virtual keyboard application will be tested from different levels below: | ||
| - | * GUI testing | + | * GUI testing |
| + | ** Cover UI testing | ||
| + | ** Better interaction with touch screen | ||
| + | ** Common UI operation | ||
| + | ** Launch with other applications(DUI and GTK application) | ||
| + | ** i18n | ||
| - | * Functional testing | + | * Functional testing |
| + | ** Work with different input method | ||
| + | ** Portrait/landscape | ||
| + | ** Visual efforts | ||
| + | ** Special symbol input support; | ||
| - | * Usage model testing | + | * Usage model testing |
| + | ** VKB work with other applications | ||
| - | * Stress testing | + | * Stress testing |
| + | ** Quickly and continuously operation | ||
| + | ** Work under high workload, UI repeat actions | ||
==Test Design== | ==Test Design== | ||
| Line 75: | Line 83: | ||
==QA Contact== | ==QA Contact== | ||
* [mailto:yi.fu@intel.com Fu Yi] | * [mailto:yi.fu@intel.com Fu Yi] | ||
| + | |||
| + | [[Category:QA]] | ||
| + | [[Category:Meego-1.1]] | ||
Contents |
This test plan is for MeeGo 1.1 HandSet UX Virtual keyboard (VKB).
The goal of Virtual Keyboard is to support multi language key input for different handset applications.
All testable features coming to MeeGo 1.1 HandSet UX virtual keyboard will be covered in this test plan.
| Feature Name | Description | Comments |
|---|---|---|
| Feature 2952 - [FEA] Virtual KeyBoard integration with Meego reference apps. | VKB integrated with MeeGo referenece apps | xxx |
| Feature 2677 - [FEA] Virtual KeyBoard with support for alpha numeric and multi language support | A Virtual keyboard is required for touch based handsets.Virtual keyboard to support alpha and numeric and multiple languages. | xxx |
there aren't features not to be tested
In general, the Virtual Keyboard test applies Black-Box test methods and refers to feature implementations to guide test design. Virtual keyboard application will be tested from different levels below: