Add-ons/QA/Testplan/Pre-installed theme in Firefox
Revision History
Date | Version | Author | Description |
---|---|---|---|
18/01/2018 | 1.0 | Cosmin Badescu | Created first draft |
Contents
Overview
The theme it is installed when the Firefox it is opened for the first time.
Purpose
This document purports to detail the test approach to Pre-installed theme in Firefox and including Entry/Exit criteria, Scope for testing, links to testcases 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 the required Telemetry is in place
- 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?
- The user experience over the pre-installed theme when the Firefox is started for the first time.
what's out of scope?
- The requirements for the download page that get handled separately.
- Performance testing.
Ownership
Dev Lead: Matt Howell ; irc nick:
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Cosmin Badescu; irc nick :CosminB
Webextensions QA: Marius Santa; irc nick :Santa
Requirements for testing
Environments
OSes covered: Windows, Mac OS X, Linux
Channel dependent settings (configs) and environment setups
Nightly
Beta
Release
Post Beta / 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 | Installing from thirdparty | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
TO-4 | Add-on updates | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
TO-5 | 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 -
- [] for Nightly builds
- [] for Beta builds
- [] for Release 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 | 18-01-2018 | |
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 | [ 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
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 - Gdocs Install flow - [Presentation] * bug 1429814 - Create custom funnelcake build that installs a given add-on during Firefox installation
ID | Priority | Component | Assigned to | Summary | Status | Target milestone |
---|---|---|---|---|---|---|
1441271 | P1 | Frontend | Andrew Swan [:aswan] | Force Firefox to show permissions/prompt for add-ons installed by the stub installer on first run | RESOLVED | mozilla60 |
1444189 | P1 | Frontend | Andrew Swan [:aswan] | Really show permissions prompts on first run from stub installer | RESOLVED | --- |
2 Total; 0 Open (0%); 2 Resolved (100%); 0 Verified (0%);
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 [ TestRail tests]
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 | 11-09-2017 | |
Test Cases Creation | ||
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 |