QA/Photon Structure
< QA
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 | |
| Marco Mucci | EPM | Product Management | TBA | |
| Gijs Kruitbosch | Software Engineer | Engineering | TBA |
Revision History
| 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 |
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
The scope of this document is to test and verify new features/bugs in Photon Structure are working as intended.
- Testing is performed on the newest version of Nightly and tested on all three mainstream operating systems of Firefox Nightly.
- (Windows, Mac OSX, and Linux - Ubuntu Distribution).
Ownership
Engineering lead: Gijs Kruitbosch
Engineering Team: Mike De Boer Drew Willcoxon
UX Team: Aaron Benson Bryan Bell
QA: Grover Wimberly IV
Testing summary
Scope of Testing
In Scope
Photon Structure - Including menus, buttons, toolbar, overflow panel, customization windows on all three major operating systems.
Out of Scope
Animations, Preferences, Onboarding, Mobile Environments
Requirements for testing
Environments
Windows 10 Ubuntu 16.04 Mac 10.12
Channel dependent settings (configs) and environment setups
Nightly
photon.structure.enabled = true (Default)
Beta
photon.structure.enabled = true
Post Beta / Release
photon.structure.enabled = 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 | Potential issues with touchscreen | 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.
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 | Bug Verification | Ensure new menus/panels open correctly | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-1 | Eng Team |
| 2 | Bug Verification | Ensure drag and drop functionality with items from new customize window can seamlessly be swapped to location bar, relevant toolbars or overflow panel | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-2, RAC-5, RAC-6 | Eng Team |
| 3 | Bug Verification | Ensure the new library menu functions as intended per specification | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-3, RAC-4 | Eng Team |
| 4 | Bug Verification | Ensure the new hamburger menu functions as intended per specification | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-4 | Eng Team |
| 5 | Bug Verification | Ensure the new page action menu functions as intended per specification | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-4 | Eng Team |
| 6 | Bug Verification | Ensure the Photon Structure menus operate correctly with RTL | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-4 | Eng Team |
| 7 | Bug Verification | Ensure the new functionality with the sidebar works as intended | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-7 | Eng Team |
| 8 | Bug Verification | Ensure the new structure works with touchscreen devices | Ensuring the bug is fixed on major desktop operating systems | Manual/Performance | RAC-8 | Eng Team |
Builds
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 | 07/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 | TBD | TBD |
| Release Date | 11/2017 with Firefox 57 | TBD |
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 | TBD |
| Test case execution | TBD |
| 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
Testcases
Test Areas
| Test Areas | Covered | Details | |
|---|---|---|---|
| Private Window | Yes | ||
| Multi-Process Enabled | Yes | ||
| Multi-process Disabled | Yes | ||
| 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 | ||
| Usability and/or discoverability testing | Yes | ||
| RTL build testing | Yes | ||
| 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 | ||
| 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 - To be worked on
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
TBD
Merge to Beta Sign-off
TBD
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | [DONE] | |
| Testing Infrastructure setup | [DONE] | |
| Test Plan Creation | IN PROGRESS | |
| Test Cases Creation | TBA | |
| Automation Coverage | N/A | |
| Performance Testing | N/A | |
| All Defects Logged | IN PROGRESS | |
| Critical/Blockers Fixed and Verified | IN PROGRESS | |
| Metrics/Telemetry | N/A | |
| Basic/Core functionality Nightly testing | IN PROGRESS | |
| QA mid-Nightly Signoff | TBA | Email to be sent |
| QA Nightly - Full Testing | IN PROGRESS | Email to be sent |
| QA pre-Beta Signoff | Email to be sent | |
| QA Beta - Full Testing | Email to be sent | |
| QA pre-Release Signoff | Email to be sent |