QA/Multi-Addon Pref
Approvals Required / Received
The following individuals are required to/have approved this Test Plan:
| Name | Title | Department | Approval Date | Method |
|---|---|---|---|---|
| Ryan VanderMeulen | QA Manager | Product Integrity | Date | |
| Blake Kaplan | Software Engineer | Engineering | Date | |
| TBD | 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 |
|---|---|---|---|
| 7/17/2017 | 1.0 | Grover Wimberly IV | Created first draft |
Overview
Purpose
- Testing and verifying the value of the pref for e10s multi add-on.
Scope
This wiki details the testing that will be performed by the project team for the e10s multi-staged rollout pref 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
- A version of Firefox 55b9 or newer.
- How testing will be performed
- Testing will be performed by the Softvision QA Las Vegas team.
Ownership
Product contact:
Engineering contact:
Blake Kaplan (IRC: mrbkap)
QA contact:
Ryan VanderMeulen (IRC: RyanVM)
QA:
PM for QA team - Rares Bologa (IRC: RaresB)
QA Engineering Contact - Grover Wimberly IV (IRC: Grover-QA)
QA - Kanchan Kumari (IRC: Kanchan_QA)
QA - Justin Williams (IRC: JW_SoftvisionQA)
QA - Stefan Georgiev (IRC: StefanG_QA)
QA - Abe Masresha (IRC: Abe_LV)
Testing summary
Scope of Testing
In Scope
Detail what is in scope from a testing perspective for the project team.
Out of Scope
Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.
Requirements for testing
Environments
- Windows 7/8/8.1/10
- Linux (Ubuntu 16.04)
- Mac OS X
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 | Risk description 1 | TO-1 | 2-Moderate | 1-Unlikely | 3-High | 6 |
| RAC-2 | Risk description 2 | TO-1 | 3-High | 3-Almost Certain | 3-High | 27 |
| RAC-3 | Risk description 3 | TO-2 | 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 | Checking preference value of dom.ipc.processCount.web | Verify the pref | Value is set to integer instead of a string | Manual Testing (Bug Verification) | RAC-1, RAC-2, RAC-3 | Eng Team |
| 2 | Ensure updates of existing users of older versions have the pref flipped | Verify the pref | Value is set to integer instead of a string for existing Firefox users | Manual Testing (Bug Verification) | RAC-1, RAC-2, RAC-3 | Eng Team |
| 3 | Monitoring the process tabs of the operating system | Verify multiple content processes are running per the pref | Multiple content processes are running simultaneously | Manual Testing (Bug Verification) | RAC-1, RAC-2, RAC-3 | Eng Team |
Builds
This section should contain links for builds with the feature -
- Links for Nightly builds
- Links for Beta builds
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 | ||
| QA - Test cases/Env preparation | ||
| 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 | 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 Release/Beta
References
- List and links for specs
List and links for available specs - documents, user stories, specifications
- Meta bug
Testcases
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | No | |
| Multi-Process Enabled | Yes | |
| Multi-process Disabled | No | |
| Theme (high contrast) | No | |
| UI | ||
| Mouse-only operation | No | |
| Keyboard-only operation | No | |
| Display (HiDPI) | No | |
| Interaction (scroll, zoom) | No | |
| Usable with a screen reader | No | e.g. with NVDA |
| Usability and/or discoverability testing | No | Is this feature user friendly |
| RTL build testing | No | |
| 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 | Yes | |
| Does sync work across upgrades | ??? | |
| Requires install testing | Yes | separate feature/application installation needed (not only Firefox) |
| Affects first-run or onboarding | Yes | 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 | ??? | |
| Locked preferences | No | |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | ??? | List of error conditions to monitor |
| Telemetry correctness testing | ??? | |
| 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 | ??? | |
| 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 | 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 | Yes (e10s multi-process) |
Test suite
Full Test suite - TBA
Bug Work
Logged bugs ( blocking 1380725 )
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Bug fix verification
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Sign off
Criteria
Checklist
- All test cases should be executed
- Preferences are set in the browser properly.
- All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/Release Management/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, if needed/available
- Regression Test suite, if needed/available
Merge to Beta 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) | ||
| Testing Infrastructure setup | ||
| Test Plan Creation | ||
| 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 | Email to be sent | |
| QA Nightly - Full Testing | ||
| QA pre-Beta Signoff | Email to be sent | |
| QA Beta - Full Testing | ||
| QA pre-Release Signoff | Email to be sent |