QA/Photon Preferences Search
Approvals Required / Received
The following individuals are required to/have approved this Test Plan:
Name | Title | Department | Approval Date | Method |
---|---|---|---|---|
Lawrence Mandel | QA Manager | Product Integrity | ||
Evan Tseng | Software Engineer | Engineering | ||
Francis Lee | EPM | Product Management |
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 |
---|---|---|---|
04/25/2017 | 1.0 | Hani Yacoub | Created first draft |
Contents
Overview
Purpose
Detail the purpose of this document. For example:
- The test scope, focus areas and objectives
- The test responsibilities
- The test strategy for the levels and types of test for this release
- The entry and exit criteria
- The basis of the test estimates
- Any risks, issues, assumptions and test dependencies
- The test schedule and major milestones
- The test deliverables
Scope
This wiki details the testing that will be performed by the project team for the Photon Preferences Search. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document what and how we shall test:
- What will be tested
- How testing will be performed
Ownership
Development Team:
Product Manager: Francis Lee
Engineer: Francis Lee (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
Roxana Leitan (irc: RoxanaLeitan) - QA
Release QA Team - Beta Testing:
Camelia Badau (irc: cbadau) - QA
Bogdan Maris (irc: bogdan_maris) - QA
Testing summary
Scope of Testing
In Scope
This feature purpose is to introduce new "search" function in Preference.
The testing effort for the Photon Preferences Search will be invested on the following areas:
- functionality: basic and advanced functionality to be verified according to the existing requirements;
- usability: search functionality must be easy to use and straightforward;
- accessibility: search functionality can be used with High Contrast Theme, Keyboard only or Screen Reader;
In the scope of current testing are following critical areas:
- General search field behavior for preferences
- Query submitted
- Hover on tooltip
- No search results
- Search highlight and Firefox support positioning
Out of Scope
- Hover state of the search field
- The state of the search field after pressing on "Enter"
- The state of the search field after clicking outside of the field
- Live search results and suggestion list
Requirements for testing
Environments
Full testing will be performed on the following OSes:
- Windows 10 x64
- Windows 7 x64
- 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 | Search field behavior could be different than the desirable one | TO-1 | 3-High | 2-Possible | 3-High | 18 |
RAC-2 | Not all search results are highlighted | TO-2 | 2-Moderate | 2-Possible | 3-High | 12 |
RAC-3 | An indicator may not correctly point the position of the result when it is hiding in a UI component | 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 | General search field behavior | Search field states and behavior should match the spec | Manual | RAC-1, RAC-2 | Eng Team |
2 | Query submitted | All search results should be highlighted according to the spec or it should show an indicator to point the position of the result when it is hiding in a UI component | Manual | RAC-1, RAC-2 | Eng Team |
3 | Hover on tooltip | Change opacity when a cursor hover on tooltips | Manual | RAC-1, RAC-2 | Eng Team |
4 | No search results | Search results page is displayed, showing a message that there are no search results | Manual | RAC-1, RAC-2 | Eng Team |
5 | Search highlight and Firefox support positioning | All search results should be highlighted according to the spec and the positioning of page element | Manual | RAC-1, RAC-2 | Eng Team |
6 | Accessibility | Ensuring that preference search functions accordingly with screen readers, in high contrast mode, and using the keyboard exclusively | Manual | RAC-1, RAC-2 | 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 | 04/25/2017 | |
Study documentation/specs received from developers | 04/25/2017 | 04/27/2017 |
QA - Test plan creation | 04/25/2017 | 07/25/2017 |
QA - Test cases/Env preparation | 04/27/2017 | 06/20/2017 |
QA - Nightly Testing | 05/08/2017 | 07/28/2017 |
QA - Beta Testing | 08/10/2017 | 09/08/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 | Test Suite |
Test case execution | Mid-Nightly56 Pre-Beta56 Pre-Release56 |
Bugs management | Bugzilla |
Status
Overview
Track the dates and build number where feature was released to Nightly: 2017-06-16 Track the dates and build number where feature was merged to Release/Beta
References
- Meta bug 1357285 - [meta] Preferences search
- List and links for specs
- Preferences Search Design
Testcases
Test Areas
Test Areas | Covered | Details | Reviewed by |
---|---|---|---|
Private Window | Yes | Francis Lee | |
Multi-Process Enabled | Yes | Francis Lee | |
Multi-process Disabled | Yes | should just check that works withour errors | Francis Lee |
Theme (high contrast) | Yes | Francis Lee | |
UI | |||
Mouse-only operation | Yes | Francis Lee | |
Keyboard-only operation | Yes | Francis Lee | |
Display (HiDPI) | Yes | Francis Lee | |
Interaction (scroll, zoom) | Yes | Francis Lee | |
Usable with a screen reader | Yes | e.g. with NVDA | Francis Lee |
Usability and/or discoverability testing | Yes | Is this feature user friendly | Francis Lee |
RTL build testing | Yes | Francis Lee | |
Help/Support | |||
Help/support interface required | Yes | Make sure link to support/help page exist and is easy reachable. | Francis Lee |
Support documents planned(written) | Yes | Make sure support documents are written and are correct. | Francis Lee |
Install/Upgrade | |||
Feature upgrades/downgrades data as expected | No | Francis Lee | |
Does sync work across upgrades | No | Francis Lee | |
Requires install testing | No | separate feature/application installation needed (not only Firefox) | Francis Lee |
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. | Francis Lee |
Does this affect partner builds? Partner build testing | No | yes/no options, add comment with details about who will lead testing | Francis Lee |
Enterprise | Raise up the topic to developers to see if they are expecting to work different on ESR builds | ||
Enterprise administration | No | Francis Lee | |
Network proxies/autoconfig | No | Francis Lee | |
ESR behavior changes | No | Francis Lee | |
Locked preferences | No | Francis Lee | |
Data Monitoring | |||
Temporary or permanent telemetry monitoring | No | List of error conditions to monitor | Francis Lee |
Telemetry correctness testing | No | Francis Lee | |
Server integration testing | No | Francis Lee | |
Offline and server failure testing | No | Francis Lee | |
Load testing | No | Francis Lee | |
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 | Francis Lee | |
Comprehensive API testing | No | Francis Lee | |
Permissions | No | Francis Lee | |
Testing with existing/popular addons | No | Francis Lee | |
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 | Francis Lee | |
Privilege escalation testing | No | Francis Lee | |
Fuzzing | No | Francis Lee | |
Web Compatibility | depends on the feature | ||
Testing against target sites | No | Francis Lee | |
Survey of many sites for compatibility | No | Francis Lee | |
Interoperability | depends on the feature | ||
Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | No | Francis Lee | |
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | No | Francis Lee | |
Interaction of this feature with other browser features | No | Francis Lee |
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: 1357285 - [meta Preferences search]
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 (2017-09-08)
List of OSes that will be covered by testing
- Windows 7 x64
- Windows 10 x64
- 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 | [DONE] | ||
Full Functional Tests Execution | [DONE] | ||
Automation Coverage | |||
Performance Testing | |||
All Defects Logged | |||
Critical/Blockers Fixed and Verified | |||
Metrics/Telemetry | |||
QA Signoff - Nightly Release | [DONE] | ||
QA Beta - Full Testing | [DONE] | ||
QA Signoff - Beta Release | [DONE] |