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 |
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:
- inform the User,if new update available
- provide aggressive visual cues to users who are majorly out of date (more than 6 weeks) that they are running an insecure version.
- users don't get option to not to check for updates, instead they have option to not apply them automatically,
- How testing will be performed:
Manual Testing
Ownership
Mozilla Development
Robert Strong
QA Eng. Softvision Las Vegas
Michelle Funches-Team Lead
Kanchan Kumari-Test Lead
Grover Wimberly IV
Abe Masresha
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
Android and iOS devices
Requirements for testing
Environments
Windows 8.1 Windows 10 Windows 7 Windows XP Ubuntu/Linux Mac OS X 10.12
Channel dependent settings (configs) and environment setups
about:config
javascript.options.asyncstack; false
browser.tabs.remote.force-enable; true
browser.tabs.remote.autostart.2; true
layers.async-pan-zoom.enabled; true
about:support
Multiprocess Windows 1/1 (Enabled by user)
Asynchronous Pan/Zoom wheel input enabled; touch input enabled
Nightly
text
Aurora
Beta
Post Beta / Release
Test Strategy
Test Objectives
Verification of Application Update UI functionality to inform users to update their old Firefox version.
Note: Port from testrail https://testrail.stage.mozaws.net/index.php?/suites/view/145&group_by=cases:section_id&group_order=asc
| Ref | Function | Test Objective | Evaluation Criteria | Test Type | Owners |
|---|---|---|---|---|---|
| 1 | Basic panning, zooming and tapping functionality | Te10s & APZ compatibility on touch enabled laptop | Make sure websites respond properly to mouse, pen/stylus, finger and keyboard when touch is enabled | Manual/Regression/ | Softvision Eng Team Las Vegas |
Builds
This section should contain links for builds with the feature -
- 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 | 10/26/2016 | |
| QA - Test cases/Env preparation | 08/25/2016 | |
| QA - Nightly Testing | ||
| 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 |
| 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
Risk analysis
It's a known issue of testing APZ with e10s enabled
Emphasis placed on exploratory testing to ensure browser functions regardless off touch, pen, or keyboard input.
References
- Meta bug 1244402
- List of APZ bugs
| Bugs | Status |
|---|---|
| 1298982 | Resolved:Fixed |
| 1298954 | Resolved:WFM |
| 1298886 | Resolved:Fixed |
| 1299243 | New |
| 1299239 | New |
| 1299249 | RESOLVED DUPLICATE of bug 1299243 |
| 1147335 | New |
| 1299286 | New |
| 1299305 | RESOLVED DUPLICATE of bug 1256677 |
| 1299625 | New |
| 1299670 | New |
| 1300203 | Resolved:Fixed |
| 1300218 | RESOLVED DUPLICATE of bug 1293483 |
| 1300874 | New |
| 1300878 | Resolved:Fixed |
| 1300905 | Resolved:Fixed |
| 1300918 | New |
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 | Done | |
| Multi-Process Enabled | Done | |
| Multi-process Disabled | Done | |
| Theme (high contrast) | ||
| UI | ||
| Mouse-only operation | Done | |
| Keyboard-only operation | Done | |
| Display (HiDPI) | ||
| Interraction (scroll, zoom) | Done | |
| Usable with a screen reader | Done | e.g. with NVIDA |
| Usability and/or discoverability testing | Is this feature user friendly | |
| RTL build testing | Done | |
| Help/Support | ||
| Help/support interface required | Make sure link to support/help page exist and is easy reachable. | |
| Support documents planned(written) | Make sure support documents are written and are correct. | |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | ||
| Does sync work across upgrades | ||
| Requires install testing | separate feature/application installation needed (not only Firefox) | |
| Affects first-run or onboarding | Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned. | |
| Does this affect partner builds? Partner build testing | yes/no options, add comment with details about who will lead testing | |
| Enterprise | Raise up the topic to developers to see if they are expecting to work different on ESR builds | |
| Enterprise administration | ||
| Network proxies/autoconfig | ||
| ESR behavior changes | ||
| Locked preferences | ||
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | List of error conditions to monitor | |
| Telemetry correctness testing | NA | |
| Server integration testing | NA | |
| Offline and server failure testing | NA | |
| Load testing | NA | |
| Add-ons | If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on. | |
| Addon API required? | NA | |
| Comprehensive API testing | ||
| Permissions | ||
| Testing with existing/popular addons | ||
| Security | Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature. | |
| 3rd-party security review | ||
| Privilege escalation testing | ||
| Fuzzing | ||
| Web Compatibility | depends on the feature | |
| Testing against target sites | ||
| Survey of many sites for compatibility | ||
| Interoperability | depends on the feature | |
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | ||
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | ||
| Interaction of this feature with other browser features |
Test suite
Full Test suite - Link with the gdoc, follow the format from link Smoke Test suite - Link with the gdoc, follow the format from link Regression Test suite - Link with the gdoc - if available/needed.
Bug Work
Tracking bug – meta bug https://bugzilla.mozilla.org/show_bug.cgi?id=1244402
Bug fix verification
| Bug No | Summary | Status | Firefox Verion |
|---|---|---|---|
| NEW | Nighly 45 | ||
Logged bugs
Bug 1298982
Bug 1298954
Bug 1298886
Bug 1299243
Bug 1299239
Bug 1299249
Bug 1147335
Bug 1299286
Bug 1299305
Bug 1299625
Bug 1299670
Bug 1300203
Bug 1300218
Bug 1300874
Bug 1300878
Bug 1300905
Bug 1300918
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
List of OSes that will be covered by testing
- Link for the tests run
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) | Done | |
| Testing Infrastructure setup | Done | |
| Test Plan Creation | Done | |
| Test Cases Creation | Done | |
| Full Functional Tests Execution | Done | |
| Automation Coverage | NA | |
| Performance Testing | NA | |
| All Defects Logged | Done | |
| 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 |