Revision History

Date	Version	Author	Description
04/25/2018	1.0	Madalin Cotetiu	Created first draft

Overview

• Make permissions visible in about:addons to users after an extension has been installed in Firefox

Purpose

This document purports to detail the test approach for the show permissions in about:addons page 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

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?

• Testing that the permissions are displayed in about:Addons for each extension
• Multiple install methods (AMO, about:addons, sideloading, add-on update)
• The displayed permissions in about:addons match the ones from the manifest (and from the install time door hanger)
• Each permission should link to the corresponding description on the SUMO page

what's out of scope?

• The end user can see when a specific extension is overwriting a Firefox setting. (this will be later implemented)

Ownership

Dev Lead: Mark Striemer; irc nick :mstriemer
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Madalin Cotetiu; irc nick :madalinc

Requirements for testing

Environments

OSes covered: Windows, Mac OS X, Linux

Channel dependent settings (configs) and environment setups

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	Permissions are displayed in about:Addons	To verify that the permissions for the extensions card are displayed correctly when installing extensions with different methods	Manual	Add-ons QA Team
TO-2	Permissions links	To verify that each permission is linked to sumo page	Manual	Add-ons QA Team

Builds

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-25-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 - Gdoc
  Feature flow - [N/A]
  

* bug 1531964 - [about:addons] Implement Permissions tab on More Options page

Full Query

ID	Priority	Component	Assigned to	Summary	Status	Resolution	Target milestone
1553794	P2	Add-ons Manager	Mark Striemer [:mstriemer]	Learn more link missing in the permission tab	RESOLVED	WONTFIX	---

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

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Installing from AMO
Installing from about:addons
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 [ Test rail Roll disco pane into about:addons]

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, critical 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	04-25-2019
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
QA Beta - Full Testing
QA Signoff - Beta Release		Email to be sent