QA/Photon Structure
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 | TBA | |
Jean Gong, Marco Mucci | EPM | Product Management | N/A | |
Jeff Griffiths, Peter Dolanjski, Justin Dolske | Engineering Manager | Product Management | 9/7/2017 | |
Gijs Kruitbosch | Software Engineer | Engineering | 9/7/2017 |
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 |
---|---|---|---|
06/28/2017 | 1.0 | Grover Wimberly IV | Created first draft |
08/10/2017 | 1.1 | Grover Wimberly IV | Added details to test plan |
08/18/2017 | 1.2 | Grover Wimberly IV | Additional revisions |
09/01/2017 | 1.3 | Grover Wimberly IV | Includes revisions from QA managers |
09/12/2017 | 1.4 | Grover Wimberly IV | Includes revisions from Project Managers |
10/04/2017 | 1.5 | Emil Ghitta | Updates |
11/06/2017 | 1.6 | Emil Ghitta | Updates |
Contents
Overview
Purpose
The purpose of this test plan is to:
- Determine the scope of testing Photon Structure related bugs and features
- Delegate test responsibilities between various QA personnel
- Have a test strategy for the levels and types of test for this release
- List entry and exit criteria
- Any risks, issues, assumptions and test dependencies
- List test schedule and major milestones
- List test deliverable(s)
Scope
This wiki section details the testing that will be performed by the project team for the Photon Structure project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document what will be tested and how testing will be performed.
Ownership
- Engineering lead:
- Engineering Team:
- UX Team:
- QA:
- Engineering Team - Nightly Testing
- Release Team - Beta/Release Testing
- Cornel Ionce (irc:cornel_ionce) - TL for QA team
- Emil Ghitta (irc:emilghitta) - QA
- Ciprian Georgiu (irc:ciprian_georgiu) -QA peer
Testing summary
Scope of Testing
In Scope
Testing will check if the functionality of the following elements work as intended:
- Menus
- Buttons
- Toolbar
- Overflow panel
- Customization window
- UI icons and elements
Testing will also check if the above targeted functionality elements work as expected using touch screen on all three major operating systems.
Out of Scope
Testing will not check:
- Animations
- Preferences
- Onboarding
Requirements for testing
Environments
- Operating systems:
- Windows 10
- Ubuntu 16.04
- Mac 10.12
- Devices: n/a
- Other configuration/environmental setup needed:
-
photon.structure.enabled
needs to be set totrue
, but it should be on by default
-
Channel dependent settings (configs) and environment setups
There are no special settings needed to test this feature, apart from its pref being set to true.
Test Strategy
Risk Assessment and Coverage
ID | Description / Threat Description | Covered by Test Objective | Magnitude | Probability | Priority | Impact Score |
---|---|---|---|---|---|---|
RAC-1 | Glitches in the new in-panel animations [when going into subviews or clicking the back button (or using the keyboard) to go back] | TO-1 | 2-Moderate | 2-Possible | 3-High | 12 |
RAC-2 | Issues with drag/drop in customize mode when dragging item to the overflow panel or toolbar/palette | TO-2 | 3-High | 3-Almost Certain | 3-High | 27 |
RAC-3 | Issues with the new library/hamburger/page action menu and items in it not functioning correctly | TO-3/4/5 | 2-Moderate | 2-Possible | 3-High | 12 |
RAC-4 | Styling issues with the new menus (page action, library, hamburger) in RTL | TO-3/4/5/6 | 2-Moderate | 1-Unlikely | 3-High | 6 |
RAC-5 | Styling/functionality issues with page actions when they're put in the location bar using the context menu on the page action menu | TO-2 | 3-High | 3-Almost Certain | 3-High | 27 |
RAC-6 | Existing buttons don't work right when pinned to the overflow panel | TO-2 | 2-Moderate | 2-Possible | 3-High | 12 |
RAC-7 | Issues relating to the sidebar - switching from one side to the other. Holding it over a restart | TO-7 | 3-High | 3-Almost Certain | 3-High | 27 |
RAC-8 | Interface not responsive to touch gestures or input | TO-8 | 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.
RAC: Refers to the "Risk Assessment and Coverage" item that is covering.
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 | Evaluation Criteria | Test Type | RAC | Owners |
---|---|---|---|---|---|---|
1 | Menu Testing | Verify that the new menus/panels open correctly | Menus and Panels are functional | Manual/Performance | RAC-1 | Eng Team |
2 | Drag-and-drop functionality/Customize Window | Verify that the drag and drop functionality with items from new customize window can seamlessly be swapped to location bar, relevant toolbars or overflow panel | The functionality of the new customize window allows the user to customize the browser without issues | Manual/Performance | RAC-2, RAC-5, RAC-6 | Eng Team |
3 | Photon library menu | Verify that the new library menu is functional as per specifications | The library menu is functional and no issues occur while interacting with it | Manual/Performance | RAC-3, RAC-4 | Eng Team |
4 | Photon hamburger window | Verify that the new hamburger menu is functional as per specifications | The new hamburger menu is fully functional and it's different options can be used without issues | Manual/Performance | RAC-4 | Eng Team |
5 | New page action window | Verify that the new page action menu is functional as per specifications | The new page action menu is functional and no issues occur | Manual/Performance | RAC-4 | Eng Team |
6 | RTL testing | Verify that the Photon Structure menus operate correctly with RTL | The Photon Structure menus are fully functional using different RTL builds | Manual/Performance | RAC-4 | Eng Team |
7 | Sidebar functionality | Verify that the new sidebar functionality works as intended | The new sidebar is fully functional and no issues occur | Manual/Performance | RAC-7 | Eng Team |
8 | Exploratory testing with touch screen | Verify the new structure works with touchscreen devices | The new structure is fully functional using touchscreen devices and no specific issues occur | Manual/Performance | RAC-8 | 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 | 06/2017 | ||
Study documentation/specs received from developers | 06/2017 | 07/2017 | |
QA - Test plan creation | 06/2017 | 08/2017 | |
QA - Test cases/Env preparation | 08/21/2017 | 08/25/2017 | |
QA - Nightly Testing | 05/2017 | 09/2017 | |
QA - Beta Testing | 09/2017 | 10/2017 | |
Release Date | 11/2017 |
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 |
Test case execution | TestRail |
Bugs management | Bugzilla |
Status
Overview
- Track the dates and build number where feature was released to Nightly
- Feature was merged to Beta - 57.0b1 (2017-09-15)
References
Testcases
Test Areas
Test Areas | Covered | Details | |
---|---|---|---|
Private Window | Yes | Test elements in Private Window (if applicable) | |
Multi-Process Enabled | Yes | Default status | |
Multi-process Disabled | Yes | If the test does not pass with e10s enabled | |
Theme (high contrast) | Yes | As needed | |
UI | |||
Mouse-only operation | Yes | As needed | |
Keyboard-only operation | Yes | As needed | |
Display (HiDPI) | Yes | As needed | |
Interaction (scroll, zoom) | Yes | As needed (Zoom Controls in Hamburger menu and Customize windows) | |
Usable with a screen reader | Yes | As applicable | |
Usability and/or discoverability testing | Yes | Verifying the buttons were functioning | |
RTL build testing | Yes | As needed | |
Help/Support | |||
Help/support interface required | Yes | Make sure link to support/help page exist and is easily reachable. | |
Support documents planned(written) | Yes | Make sure support documents are written and are correct. | |
Install/Upgrade | |||
Feature upgrades/downgrades data as expected | N/A | ||
Does sync work across upgrades | Yes | As needed | |
Requires install testing | N/A | ||
Affects first-run or onboarding | N/A | ||
Does this affect partner builds? Partner build testing | No | ||
Enterprise | Raise up the topic to developers to see if they are expecting to work different on ESR builds | ||
Enterprise administration | N/A | ||
Network proxies/autoconfig | N/A | ||
ESR behavior changes | N/A | ||
Locked preferences | N/A | ||
Data Monitoring | |||
Temporary or permanent telemetry monitoring | No | List of error conditions to monitor | |
Telemetry correctness testing | N/A | ||
Server integration testing | N/A | ||
Offline and server failure testing | N/A | ||
Load testing | N/A | ||
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 | Yes | ||
Permissions | No | ||
Testing with existing/popular addons | Gecko Profiler and relevant Web Extensions | ||
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 | No | ||
Web Compatibility | depends on the feature | ||
Testing against target sites | Yes | ||
Survey of many sites for compatibility | Yes | ||
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 | Desktop Only | ||
Interaction of this feature with other browser features | Yes |
Test suite
- Full Test suite - TestRail link
Bug Work
Meta bug: 1387512 - [Meta Photon Structure QA Tracking Bug]
Logged bugs ( blocking 1387512 )
133 Total; 0 Open (0%); 6 Resolved (4.51%); 127 Verified (95.49%);
Bug fix verification
128 Total; 0 Open (0%); 1 Resolved (0.78%); 127 Verified (99.22%);
Sign off
Criteria
Checklist
- All bugs are to be verified
- All test cases should be executed
- 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:
- Windows 10 Surface Pro Touchscreen
- Windows 10 64bit
- Windows 7 64bit
- Ubuntu 16.04 64bit
- MacOS 10.11
- Link for the tests run -link
Merge to Beta Sign-Off
- List of OSes that will be covered by testing
- macOS 10.12
- Ubuntu 16.04 64bit
- Windows 7 64bit
- Windows 10 64bit
Checklist
Exit Criteria | Status | Notes/Details |
---|---|---|
Testing Prerequisites (specs, use cases) | [DONE] | |
Testing Infrastructure setup | [DONE] | |
Test Plan Creation | [DONE] | |
Test Cases Creation | [DONE] | |
Automation Coverage | N/A | |
Performance Testing | N/A | |
All Defects Logged | [DONE] | |
Critical/Blockers Fixed and Verified | IN PROGRESS | |
Metrics/Telemetry | N/A | |
Basic/Core functionality Nightly testing | [DONE] | |
QA mid-Nightly Signoff | [DONE] | Email Sent on 2017.08.26 |
QA Nightly - Full Testing | [DONE] | |
QA pre-Beta Signoff | [DONE] | Email sent on 2017.09.15 |
QA Beta - Full Testing | [DONE] | |
QA pre-Release Signoff | [DONE] | Email Sent on 2017.10.27 |