QA/B2G/How To Test Firefox OS/Keyboard
From MozillaWiki
< QA | B2G | How To Test Firefox OS
Contents
Keyboard
Stability (Open to Test)
- Link to: Developer's status
How to test this App
- Link to: One and Done Items
- Keyboard Application Coverage
- Access Points
- Messages
- Contacts
- Browser
- Dialer
- Lockscreen
- SIM Pin
- Clock
- Calendar
- Usage
- Marketplace
- Loop
- Rocketbar
- FTE
- Settings
- Data Management
- Installed 3rd-Party Keyboards
- Customized Keyboards pushed to the phone
- Areas to test
- QWERTY Keyboard
- Dial Pad
- Passcode pad
- Numeric Keybaord
- Third Party Keyboard
- Data Usage (Considered a fake keyboard)
- Screen Lock (Considered a fake keyboard)
- User Actions
- Keyboard Tips
- Long Press Characters to reveal special characters
- Double tap shift key to enable shift lock
- Double tap Space bar to add a "." and a space
- Long press Space bar to dismiss keyboard
- Tap "12&" to change characters available, then "Alt" to change once more
- Tap Language code, Ex: "En" (To the left of spacebar) to change keybaord language
- Tapping spacebar when a word is suggested
- Keyboard Tips
- Positive & Negative Testing
- Positive Examples
- Type out a sentence
- Double tap Space bar to finish the sentence and begin the next
- Change the Keyboard Language
- Enable shift lock
- Negative Examples
- Triple Tapping the Space bar to give extra periods ex: ".."
- Long pressing a character and then selecting another character
- Boundary Testing
- http://en.wikipedia.org/wiki/Boundary_testing
- Typing really fast
- Typing with 20+ different keyboards
- http://en.wikipedia.org/wiki/Boundary_testing
- Race Conditions
- http://en.wikipedia.org/wiki/Race_condition
- Opening multiple keyboards within the same app (Editing a contacts phone and name)
- http://en.wikipedia.org/wiki/Race_condition
- Notes
- With low memory settings (319MB memory) the keyboard will run in process, instead of as a separate process
- Users can add Keyboards with different Languages using this link: Keyboard Customization
FXOS Contacts
- Team Members
- Keyboard QA Owner
- Gerry Chang
Fixed in last 7 days
Open Bugs
Last 7 days |
---|
Bugzilla query error
|
All open bugs |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
All open blockers/noms |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
Sprint Details
Design Documents
- UX Specs
- Building Blocks
User Stories Metas
All Metas |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
Open User Stories |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
All User Stories |
---|
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
Setup
- 1. Open an app that contains a Keyboard
Automation Scripts
- How to Run Automation
- gaiatest --testvars=gaiatest/testvars.json --address=localhost:2828 --restart --timeout=100000 gaiatest/tests/functional/keybaord/manifest.ini
- Automated Keyboard Smoketests
- None
- All Gaia-UI Functional Tests
- Unit Tests
- n/a
Logging
- Please provide the logcat by running adb logcat -v time -s GeckoDump:V Gecko:V GeckoConsole:V OomLogger:V | tee FILENAME-TO-LOG-TO. Please start running this command BEFORE you attempt to reproduce the problem. logcat uses a circular buffer that discards older entries when the buffer fills up, so if you run logcat only after the problem happens, you may not have all of the logic. Once you are done, hit control-C and send us the file.
Bug Writing
- Link to Bug Writing Document