QA/Photon Preferences Visual Refresh
Approvals Required / Received
The following individuals are required to/have approved this Test Plan:
Name | Title | Department | Approval Date | Method |
---|---|---|---|---|
Lawrence Mandel/Ryan VanderMeulen | QA Reviewer | Product Integrity | Date | |
Tim Chien | Software Engineer | Engineering | Date | |
Marco Mucci | EPM | Product Management | Date |
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 |
---|---|---|---|
08/10/2017 | 1.0 | Hani Yacoub | Created first draft |
Contents
Overview
Purpose
The purpose of this feature is to redesign all UI components on the Preferences page (about:preferences) to Photon style.
Scope
The scope of testing will be covering the UI components on the Preferences page (Navigation menu, Search in preferences, Content area - General, Content area - search, Content area - Privacy & Security, Content area - Firefox account) implementation according to specifications.
Ownership
Development Team:
Product Manager: Francis Lee
Engineer: Evan Tseng (irc: evanxd)
Engineer: Ricky Chien (irc: rickychien)
Engineering Team - Nightly Testing:
Rares Bologa (irc: RaresB) - PM for QA team
Brindusa Tot (irc: brindusat) - leading QA efforts
Hani Yacoub (irc: hani) - QA
Release QA Team - Beta Testing:
Camelia Badau (irc: cbadau) - QA
Bogdan Maris (irc: bogdan_maris) - QA
Testing summary
Scope of Testing
In Scope
In the scope of current testing are following areas:
- Font family, color (*it will be verified by a designer's UI review)
- Background color (*it will be verified by a designer's UI review)
- Web components: checkbox, radio button, input field, button, dropdown menu (*it will be verified by a designer's UI review)
- Update and add icons/images from:
- menu
- firefox account
- add content and images on sub-pages in Preferences
- Search function
- Remove search result icon
- Check element alignment visually
- RWD
Out Of Scope
We are not testing the functionality of the preferences page.
Requirements for testing
Environments
Full testing will be performed on the following OSes:
- Windows 10 x64
- Windows 7 x86
- Mac OS X 10.12
- Ubuntu 16.04
Channel dependent settings (configs) and environment setups
Nightly
text
Beta
text
Post Beta / Release
text
Test Strategy
Risk Assessment and Coverage
ID | Description / Threat Description | Covered by Test Objective | Magnitude | Probability | Priority | Impact Score |
---|---|---|---|---|---|---|
RAC-1 | Preferences page behavior | TO-1 | 3-High | 2-Possible | 3-High | 18 |
RAC-2 | UI components of the navigation bar could not match the spec | TO-2 | 2-Moderate | 2-Possible | 3-High | 12 |
RAC-3 | UI components of the search section could not match the spec | TO-3 | 2-Moderate | 2-Possible | 3-High | 12 |
RAC-4 | UI components of the content area could not match the spec | TO-3 | 2-Moderate | 2-Possible | 3-High | 12 |
Values:
- Magnitude: 1- Low , 2-Moderate, 3-High
- Probability: 1-Unlikely, 2-Possible, 3-Almost Certain
- Priority: 1 - Low, 2-Medium, 3-High
Impact Score Breakdown:
- An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
- An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
- An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.
Test Objectives
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master. This could be documented in bullet form or in a table similar to the one below.
Ref | Function | Test Objective | Test Type | RAC | Owners |
---|---|---|---|---|---|
1 | Navigation | UI components of the navigation bar are correctly displayed according to the spec | Manual | RAC-1, RAC-2 | Eng Team |
2 | Search in Preferences | UI components of the Search in Preferences are correctly displayed according to the spec | Manual | RAC-1, RAC-3, RAC-4 | Eng Team |
3 | Content Area | UI components of the Content Area are correctly displayed according to the spec | Manual | RAC-1, RAC-4 | Eng Team |
4 | Accessibility | Testing for accessibility includes:
- testing using high Contract themes |
Manual | RAC-1, RAC-2, RAC-3, RAC-4 | Eng Team |
Builds
This section should contain links for builds with the feature -
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
Project phase | Start Date | End Date |
---|---|---|
Start project | 08/10/2017 | |
Study documentation/specs received from developers | 08/10/2017 | 08/14/2017 |
QA - Test plan creation | 08/10/2017 | 08/21/2017 |
QA - Test cases/Env preparation | 08/14/2017 | |
QA - Nightly Testing | ||
QA - Beta 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 | Test Suite |
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 Release/Beta
References
- Meta bug 1357306 - [meta] Preferences visual refresh
- List and links for specs
- Preferences Visual Refresh
Testcases
Test Areas
Test Areas | Covered | Details | Reviewed by |
---|---|---|---|
Private Window | Yes | ||
Multi-Process Enabled | No | ||
Multi-process Disabled | No | should just check that works withour errors | |
Theme (high contrast) | Yes | ||
UI | |||
Mouse-only operation | Yes | ||
Keyboard-only operation | Yes | ||
Display (HiDPI) | Yes | ||
Interaction (scroll, zoom) | Yes | ||
Usable with a screen reader | Yes | e.g. with NVDA | |
Usability and/or discoverability testing | Yes | Is this feature user friendly | |
RTL build testing | Yes | ||
Help/Support | |||
Help/support interface required | No | Make sure link to support/help page exist and is easy reachable. | |
Support documents planned(written) | No | Make sure support documents are written and are correct. | |
Install/Upgrade | |||
Feature upgrades/downgrades data as expected | No | ||
Does sync work across upgrades | No | ||
Requires install testing | No | separate feature/application installation needed (not only Firefox) | |
Affects first-run or onboarding | No | 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 | No | 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 | No | ||
Network proxies/autoconfig | No | ||
ESR behavior changes | No | ||
Locked preferences | No | ||
Data Monitoring | |||
Temporary or permanent telemetry monitoring | No | List of error conditions to monitor | |
Telemetry correctness testing | No | ||
Server integration testing | No | ||
Offline and server failure testing | No | ||
Load testing | No | ||
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? | No | ||
Comprehensive API testing | No | ||
Permissions | No | ||
Testing with existing/popular addons | No | ||
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 | No | ||
Privilege escalation testing | No | ||
Fuzzing | Mo | ||
Web Compatibility | depends on the feature | ||
Testing against target sites | No | ||
Survey of many sites for compatibility | No | ||
Interoperability | depends on the feature | ||
Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | No | ||
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | No | ||
Interaction of this feature with other browser features | No |
Test suite
Full Test suite - Link to test rail - tascases should be added under Firefox Desktop project link Smoke Test suite - Link with the tests - if available/needed. Regression Test suite - Link with the tests - if available/needed.
Bug Work
Meta bug: 1357306 - [meta Preferences visual refresh]
Bug fix verification
61 Total; 4 Open (6.56%); 30 Resolved (49.18%); 27 Verified (44.26%);
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, criticals 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
- Full Test suite, link to TestRail - Tests Runs and Results link
- Daily Smoke, lif needed/available
- Regression Test suite, if needed/available
Pre-Release Sign-Off ()
List of OSes that will be covered by testing
- Windows 7 x64
- Windows 10 x86
- macOS 10.12
- Ubuntu 16.04 x64
- Link for the tests run
- Full Test suite - Tests Runs and Results link
Checklist
Exit Criteria | Status | Notes/Details |
---|---|---|
Testing Prerequisites (specs, use cases) | [DONE] | |
Testing Infrastructure setup | [DONE] | |
Test Plan Creation | [DONE] | |
Test Cases Creation | ||
Automation Coverage | ||
Performance Testing | ||
All Defects Logged | ||
Critical/Blockers Fixed and Verified | ||
Metrics/Telemetry | ||
Basic/Core functionality Nightly testing | ||
QA mid-Nightly Signoff | ||
QA Nightly - Full Testing | ||
QA pre-Beta Signoff | ||
QA Beta - Full Testing | ||
QA pre-Release Signoff |