Add-ons/QA/Testplan/telemetry on aboutaddons

From MozillaWiki
Jump to: navigation, search

Revision History

Date Version Author Description
03-05-2019 1.0 Vlad Jiman Updated all sections


We should add telemetry to the about:addons page to help us identify usage of the page's UI (rather than just events that happen via the UI).


This document purports to detail the test approach to telemetry for about:addons page, including 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 have 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 triggers are in place
  • 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?

  • Validation of the Telemetry for about:addons feature along with all of the attached UI features.

what's out of scope?

  • Security testing
  • Device testing


Dev Lead: Mark Striemer ; irc nick:mstriemer
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Vlad Jiman; irc nick :VladJ

Requirements for testing


OSes covered: Windows

Channel dependent settings (configs) and environment setups


security.signed_app_signatures.policy with the default value 2


security.signed_app_signatures.policy with the default value 2


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.

The objective of testing this feature is to assure that the triggers (Listed here: are correctly logging user events.


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 10/18/2018
Study documentation/specs received from developers 03/05/2019
QA - Test plan creation 03/05/2019
QA - Test cases/Env preparation 03/05/2019
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
Test case execution [TestRail
Bugs management Bugzilla



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
  Trigger list - Gdocs
* bug 1505924 - [meta] New about:addons interface
Full Query
ID Priority Component Assigned to Summary Status Target milestone
1514316 P2 Add-ons Manager Mark Striemer [:mstriemer] Setup a new about:addons behind a pref VERIFIED mozilla67
1525090 P2 Add-ons Manager Mark Striemer [:mstriemer] Use AddonListeners for HTML about:addons views VERIFIED mozilla67
1530530 P2 Add-ons Manager Show something when there are no add-ons installed NEW ---
1533795 P1 Add-ons Manager Mark Striemer [:mstriemer] [meta] about:addons interface changes [phase 1] NEW ---

4 Total; 2 Open (50%); 0 Resolved (0%); 2 Verified (50%);



Summary of testing scenarios

Test Areas

Test Areas Covered Details
Private browsing
Profile testing
System toggled ON/OFF
Performance testing
Cookie's round trip validation

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, Criticals 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-01-2019
Test Cases Creation
Full Functional Tests Execution
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
QA Signoff - Nightly Release Email to be sent
QA Beta - Full Testing
QA Signoff - Beta Release Email to be sent