From MozillaWiki
Jump to: navigation, search

Test Plan


Design Documentation/Background Research

The purpose of the virtual keyboard is to provide an interface to fennec for people to type in various languages when a hardware keyboard is closed or not available to the device.

Description of this Document

This document will cover the testing approach for virtual keyboards on the Tablets. This document will not cover the testing approach for smaller handheld device, but may be using most of the same techniques for testing VKB for smaller handheld devices. There are some notable differences, such as the virtual keyboard is not full screen for landscape view.

Related Documents

See Virtual Keyboard for Android Test Plan

Schedule and Milestones

See Feature Page

Resource Requirements


Test devices: Handhelds for comparison:

  • Motorola Droid 2
  • HTC Thunderbolt


  • HTC Flyer
  • Samsung

System Testing

  • Android OS 2.2 (Froyo)
  • Android OS 2.3 (Gingerbread)
  • Android OS 3.1 (Honeycomb)


Variety of VKB/IMEs  : see...


Feature Lead


  • Testing Devices
  • Training other people in VKBs when asked
  • Verifying unconfirmed bugs
  • triaging bugs
  • verifying fixes


  • none necessary


  1. need to know how to install VKBs
  2. need to know how the VKB works

Features To Be Tested / Test Approach

New Features Testing

The VKB has a slightly different behavior on the Tablet platform. The differences are listed within the bug list and the ui design described in the main feature page
The test outline below will show the items to be tested.

Regression Testing

Features Not To Be Tested

Test Deliverables

  • Bug Reports
  • Bug verifications
  • Litmus Test cases


  • Change in theme may alter some of the ways to bring up the keybaord
  • VKBs are generally third party, and some crashes may be caused by the interaction between the VKB and Fennec
  • VKB bugs are not the same as IME bugs and vice versa; knowing the differences between the two can be hard without a developer looking into it.

Entrance/Exit Criteria

  • The top 3 keyboards, an Asian keyboard (winCE?) and European Keyboard does not have any crashers, hangers, etc.

Test Outline

Note :

  1. This test out line is a brain storm of all possible conditions to consider for testing. The scope of the testing will be narrowed from this list based on design information, risks of breakage, etc.
  2. When testing, each item has to be checked, for performance, visual impact (ie graphic defects), race conditions, locking, etc. Some things will be called out to have specific instructions to check for, however the testing should not be limited to only the called out item.

Positive Smoke/Alpha Tests


  1. General


1. UI Based Functionality

2. Conditional Functionality

Beta Conditional