QA/Application Update UI
Revision History
This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded). The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.
Date | Version | Author | Description |
---|---|---|---|
11/16/2016 | 1.0 | Kanchan Kumari | Created first draft |
Contents
Overview
Purpose
- To test Firefox Application Update UI feature.
Scope
- This wiki details the testing that will be performed by project team for Firefox Application Update UI feature. It defines the overall testing requirements and provides an integrated view of the project test activities. The purpose is to document:
What will be Tested:
- Notify the user when update is available for Firefox
- Different options to update Firefox
- Firefox update failures due to various reasons
- Notify user in case of update failure and provide download option
- Set of doorhangers for various update failure conditions
- Doorhanger UI in full screen mode and different window sizes
- How testing will be performed:
Manual Testing
Ownership
Mozilla Development
Robert Strong]
QA Eng. Softvision Las Vegas
Stefan Georgiev - Team Lead ]
Kanchan Kumari - Test Lead
Abe Masresha
Grover Wimberly IV
Justin Williams
Testing summary
Scope of Testing
In Scope
This feature will be tested manually on Windows, Mac OS X and Linux operating systems
Out of Scope
<TBD>
Requirements for testing
Environments
Windows 10
Windows 7
Ubuntu/Linux
Mac OS X 10.12
Channel dependent settings (configs) and environment setups
Nightly
Aurora
Beta
Post Beta / Release
Risk Analysis
Risk areas |
---|
Users may not be notified correctly in case of Firefox update failures, for e.g. when an end user without appropriate permission tries to install Firefox and it fails without notifying the user correctly. |
Test Strategy
Test Objectives
Verification of Application Update UI functionality
Note: Port from Testrail
Ref | Function | Test Objective |
---|---|---|
1 | Hamburger Badge | Verify hamburger badge when update is available |
2 | Doorhanger UI | Verify doorhanger ui for various update and download condition |
3 | "Not Now" button | Verify Clicking "Not Now" in the doorhanger ui should dismiss the doorhanger ui |
4 | "Restart and Restore" button | Verify Clicking the "Restart and Restore" in the doorhanger ui should restart and apply the update |
5 | Application Update UI in Fullscreen mode | Verify new doorhanger display when placing the mouse at the top of the screen to temporarily exit fullscreen |
6 | Notification in case of update failure | Verify user gets notification in case of update failure |
7 | Download option for user in case of update failure | Verify user gets option to download fresh copy of application |
Builds
- Links for Nightly builds https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
Project phase | Start Date | End Date |
---|---|---|
Start project | ||
Study documentation/specs received from developers | ||
QA - Test plan creation | 04/12/2017 | |
QA - Test cases/Env preparation | 04/12/2017 | |
QA - Nightly Testing | 04/14/2017 | |
Release Date |
Testing Tools
Detail the tools to be used for testing, for example see the following table:
Process | Tool |
---|---|
Test plan creation | Mozilla wiki |
Test case creation | testrail/ Google docs |
Test case execution | testrail/ Google docs |
Bugs management | Bugzilla |
Status
Overview
Track the dates and build number where feature was released to Nightly Track the dates and build number where feature was merged to Aurora Track the dates and build number where feature was merged to Release/Beta
References
- Meta bug 893505
Testcases
Overview
Websites respond properly to mouse, keyboard, pen/stylus, finger with touch enabled Long pressing to do text selection, menus, scrolling and dragging etc with fingers, stylus and mouse
Test Areas
Test Areas | Covered | Details |
---|---|---|
Private Window | Yes | |
Multi-Process Enabled | Yes | |
UI | ||
Usability and/or discoverability testing | Yes | Is this feature user friendly |
RTL build testing | Yes | |
Install/Upgrade | ||
Feature upgrades/downgrades data as expected | Yes | |
Requires install testing | Yes | |
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | Partial |
Test suite
Full Test suite - https://docs.google.com/spreadsheets/d/1vIGMlBWjlBFNw_-JbK_98skmAv49_8MGpTEUR8ftYzg/edit#gid=0
Bug Work
Tracking bug – meta bug https://bugzilla.mozilla.org/show_bug.cgi?id=893505
Bug fix verification
Bug No | Summary | Status | Firefox Verion |
---|---|---|---|
NEW | Nighly | ||
Logged bugs
TBD
Sign off
Criteria
Check list
- All test cases should be executed
- Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
- All blockers and critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)
Results
Nightly testing
Testing was executed on following OSes:
Windows 10
Windows 7
Ubuntu/Linux
Mac OS X 10.12
- Link for the tests run
- Full Test suite, use template from link
Merge to Aurora Sign-off
List of OSes that will be covered by testing
- Link for the tests run
- Full Test suite
Checklist
Exit Criteria | Status | Notes/Details |
---|---|---|
Testing Prerequisites (specs, use cases) | ||
Testing Infrastructure setup | ||
Test Plan Creation | In Progress | |
Test Cases Creation | ||
Full Functional Tests Execution | ||
Automation Coverage | NA | |
Performance Testing | NA | |
All Defects Logged | ||
Critical/Blockers Fixed and Verified | ||
Metrics/Telemetry | ||
QA Signoff - Nightly Release | Email to be sent | |
QA Aurora - Full Testing | ||
QA Signoff - Aurora Release | Email to be sent | |
QA Beta - Full Testing | ||
QA Signoff - Beta Release | Email to be sent |