Add-ons/QA/Testplan/Identifying recommended extensions in about:addons

From MozillaWiki
Jump to: navigation, search

Revision History

Date Version Author Description
04/15/2018 1.0 Cosmin Badescu Created first draft


  • Extensions will be signed with additional metadata so Firefox can recognize if they are marked as Recommended or Partner.
  • The Recommended Extensions PRD explains why this new distinction is important. The signature changes are necessary so Firefox can independently assess the extension regardless of how it was installed. Storing this data in the signature also protects it from being tampered with.


This document purports to detail the test approach for the improvements of Local Storage API 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


This section describes what parts of the feature will be tested and what parts won't be.

what's in scope?

  • Recommended extensions will be identified in Firefox in about:addons by an additional graphic/text on the universal card. As such, this is a slight feature to QA. We only need to verify that recommended extensions, once installed, are correctly displayed in about:addons.

what's out of scope?

  • Security testing


Dev Lead: Mark Striemer; irc nick :mstriemer
Dev Lead: Andrew Swan; irc nick :aswan
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Cosmin Badescu; irc nick :CosminB

Requirements for testing


OSes covered: Windows, Mac OS X, Linux

Channel dependent settings (configs) and environment setups


  • N/A


  • N/A


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 recommendation badges are displayed correctly Manual Add-ons QA Team
TO-2 Installing from local files To verify that the recommendation badges are displayed correctly Manual Add-ons QA Team
TO-3 Add-on updates To verify that the recommendation badges are displayed correctly Manual Add-ons QA Team
TO-4 Sideloading To verify that the recommendation badges are displayed correctly Manual Add-ons QA Team


This section should contain links for builds with the feature -

  • Link for Nightly builds
  • Link for Beta builds
  • Link 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 04-15-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



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


* List and links for specs
  PRD - Gdoc
  Feature flow - Mocks

* bug 1539699 - [about:addons] identify recommended extensions in about:addons
Full Query
ID Priority Component Assigned to Summary Status Resolution Target milestone
1540253 P2 Add-ons Manager Identify extensions as recommended when they're installed NEW ---

1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);



Summary of testing scenarios

Test Areas

Test Areas Covered Details
Installing from AMO
Installing from local files
Installing from thirdparty
Add-on updates

Test suite

  • Link for the [ Initial test planning]
  • Link for the [ Google doc tests]
  • Link for the [ Test rail Identifying recommended extensions in about:addons]

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


Check list

  • All test cases should be executed
  • Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
  • All blockers, critical must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)


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


Exit Criteria Status Notes/Details
Testing Prerequisites (specs, use cases)
Testing Infrastructure setup
Test Plan Creation 04-15-2019
Test Cases Creation
Full Functional Tests Execution
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
QA Signoff - Nightly Release
QA Beta - Full Testing
QA Signoff - Beta Release Email to be sent