Add-ons/QA/Testplan/Abuse reporting in about:addons: Difference between revisions
| Line 150: | Line 150: | ||
== Risk analysis == | == Risk analysis == | ||
Question about providing client ID and installation date to AMO for an AMO-based flow vs bridging the AMO-based flow with the Firefox one to create one UX. | Question about providing client ID and installation date to AMO for an AMO-based flow vs bridging the AMO-based flow with the Firefox one to create one UX. | ||
Identify the high-risk assumptions | Identify the high-risk assumptions | ||
Identify existing bugs on the feature with high risk | Identify existing bugs on the feature with high risk | ||
Revision as of 13:50, 14 May 2019
Revision History
| Date | Version | Author | Description |
|---|---|---|---|
| 02/14/2018 | 1.0 | Cosmin Badescu | Created first draft |
Overview
- In order to increase monitoring of unlisted Firefox extensions and user security, we are implementing a new abuse report feature in the Firefox Add-ons Manager. It will allow users to report add-ons they have installed or recently removed. It includes report categorization features that will also be implemented on AMO for consistency and better report quality.
Purpose
This document purports to detail the test approach for the Abuse reporting in about:addons feature and includes Entry/Exit criteria, Scope for testing, links to test cases etc
Entry Criteria
- QA has access to all the PRDs, mocks and related documents
- The feature has landed on Nightly
- AMO parts has landed on dev
Exit Criteria
- All the bugs against the feature have been triaged
- All the P1/P2 bugs have been fixed
- All the resolved bugs have been verified by QA
- The find/fixed rate is going down over a predefined period of time
Acceptance Criteria
This section broadly outlines when the product is ready to ship
- QA has signed off
- All info is localized at least for a pre-defined set of locales
- All the necessary PR/blogposts have been sent out
Scope
This section describes what parts of the feature will be tested and what parts won't be.
what's in scope?
- This is a cross-platform feature that is not limited to any specific operating systems or locales. QA for this should be straightforward: confirming that all abuse reporting user flows function as expected.
As this is a new feature, there should be unit test coverage provided as part of the development effort; in addition, there are no existing issues that need to be resolved for this, and mitigation of any blocking issues discovered in QA should be as simple as not enabling the pref for release.
what's out of scope?
- Security testing
Ownership
Dev Lead: Luca Greco; irc nick :rpl
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Victor Carciu; irc nick :VictorC
AMO QA: Alexandra Moga; irc nick :LexaSV
Requirements for testing
Environments
OSes covered: Windows, Mac OS X, Linux
Channel dependent settings (configs) and environment setups
Nightly
- Enable extensions.htmlaboutaddons.enabled from about:config
Beta
- Enable extensions.htmlaboutaddons.enabled from about:config
Release
The feature is enabled by default
Test Strategy
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 | Owners |
|---|---|---|---|---|
| TO-1 | Installing from AMO | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
| TO-2 | Installing from local files | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
| TO-3 | Add-on updates | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
| TO-4 | Sideloading | To verify that the extension uses the API correctly | Manual | Add-ons QA 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 | ||
| Study documentation/specs received from developers | ||
| QA - Test plan creation | 05-14-2018 | |
| QA - Test cases/Env preparation | 05-16-2018 | N/A |
| QA - Nightly Testing | N/A | N/A |
| QA - Beta Testing | 05-20-2018 | |
| 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 | [ Docs] / TestRail |
| Test case execution | [ Docs] / [ TestRail] |
| Bugs management | Bugzilla / Github |
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
Risk analysis
Question about providing client ID and installation date to AMO for an AMO-based flow vs bridging the AMO-based flow with the Firefox one to create one UX. Identify the high-risk assumptions Identify existing bugs on the feature with high risk Identify if other areas are affected by the fix
References
* List and links for specs PRD - [] Install flow - N/A
* bug 1505924 - [meta] New about:addons interface
30 Total; 8 Open (26.67%); 15 Resolved (50%); 7 Verified (23.33%);
Testcases
Overview
Summary of testing scenarios
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Installing from AMO | ||
| Installing from local files | ||
| Installing from thirdparty | ||
| Add-on updates | ||
| Sideloading | ||
| Other |
Test suite
- Link for the [ Initial test planning]
- Link for the [ Google doc tests]
- Link for the about:addons_non-xul_rebuild
Bug Work
Tracking bug - []
Bug fix verification
[Verified] [ Bug xxxxxxx] - Display permissions prompt for webextensions installed using mozAddonManager
- ↳ 2017-01-10: verified fixed on 53.0a1 across platforms
[Verified] [ Bug xxxxxxx] - Prompt users with permissions for third-party webextensions installs
- ↳ 2015-04-21: verified fixed on 53.0a1 across platforms
Logged bugs
[ Bug xxxxxxx] - Misaligned icon and webextension name in permissions doorhanger
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, use template from []
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 | 02-14-2019 | |
| Test Cases Creation | 02-13-2019 | N/A |
| Full Functional Tests Execution | ||
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | ||
| Critical/Blockers Fixed and Verified | ||
| Metrics/Telemetry | ||
| QA Signoff - Nightly Release | Email to be sent | |
| QA Beta - Full Testing | ||
| QA Signoff - Beta Release | Email to be sent |