Add-ons/Webextensions Cutover/Testplan

Revision History

Date	Version	Author	Description
01/09/2017	1.0	Krupa Raj	Created first draft
01/20/2017	1.1	Vasilica Mihasca	Updates
01/23/2017	1.2	Krupa Raj	Added Acceptance Criteria
03/22/2017	1.3	Vasilica Mihasca	Added TestRail links

Overview

Permissions is a feature which allows webextensions to have certain special powers. The permissions key specified in the manifest.json will grant special powers for your extension. This key is an array of strings, and each string is a request for a permission.

If you request permissions using this key, then the browser may inform the user at install time that the extension is requesting certain privileges, and ask them to confirm that they are happy to grant these privileges. The browser may also allow the user to inspect an extension's privileges after installation.

Purpose

This document purports to detail the test approach to Webextension Permissions 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?

• Installation flow from AMO
• Installation flow from Add-ons Manager
• Installation flow from Discopane
• Installation flow from Third-party websites
• Add-on updates
• Add-on Validation related to permissions during submission
• Sideloading(?)
• Webextensions have access to the permissions requested

what's out of scope?

• Security testing
• Performance testing

Ownership

Dev Lead: Andrew Swan; irc nick :aswan
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Vasilica Mihasca; irc nick :vasilica_mihasca
Add-ons QA: Valentina Peleski; irc nick :ValentinaV

Requirements for testing

Environments

OSes covered: Windows, MacOSX, Linux

Channel dependent settings (configs) and environment setups

Nightly

• Enable extensions.webextPermissionPrompts from about:config
• Disable check for signing if testing on AMO dev or stage

Aurora

• Enable extensions.webextPermissionPrompts from about:config
• Disable check for signing if testing on AMO dev or stage

Beta

• Enable extensions.webextPermissionPrompts from about:config
• [Unbranded build] Disable check for signing if testing on AMO dev or stage

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	Evaluation Criteria	Test Type	Owners
TO-1	Validation during AMO	To verify that linter raise the proper error messages	Manual	Add-ons QA Team
TO-2	AMO public pages	To verify that permissions are correctly displayed	Manual	Add-ons QA Team
TO-3	Installing from AMO	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team
TO-4	Installing from Discopane	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team
TO-5	Installing from Add-ons manager	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team
TO-6	Installing via sideloading	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team
TO-7	Installing from local files	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team
TO-8	Installing from thirdparty	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team
TO-9	Add-on updates	To verify that the permissions flow is fully respected	Manual	Add-ons QA Team

Builds

This section should contain links for builds with the feature -

• Link for Nightly builds
• Link for Aurora builds
• Link for Beta 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	01-09-2017	01-11-2017
QA - Test cases/Env preparation	01-09-2017
QA - Nightly Testing	01-11-2017
QA - Aurora 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 / Google docs / etherpad
Test case execution	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 Aurora
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
  wiki - https://wiki.mozilla.org/Add-ons/Firefox57

* bug 1352204 - Only allow webextension and MPC=true (which=no shims) add-ons on Nightly

Full Query

ID	Priority	Component	Assigned to	Summary	Status	Target milestone
1356027	--	Add-ons Manager	Andrew Swan [:aswan]	Add pref that disables loading any extensions without MPC=true	RESOLVED	mozilla55
1356462	--	Add-ons Manager	Andrew Swan [:aswan]	about:addons indications for disabled non-MPC extensions	RESOLVED	mozilla55
1358620	P1	Add-ons Manager	Andrew Swan [:aswan]	Add telemetry for non-MPC extensions	RESOLVED	mozilla55
1359476	P1	Add-ons Manager	Andrew Swan [:aswan]	Dictionaries are getting disabled as not multi process compatible	VERIFIED	mozilla55
1360169	--	Add-ons Manager		Incorrect error message for ZoomFox add-on in about:addons	RESOLVED	---
1360172	--	Add-ons Manager		Multiprocess Compatible error displayed for all add-ons and webextensions from about:addons search list	RESOLVED	---
1360687	--	Marionette	Henrik Skupin [:whimboo][⌚️UTC+2]	Update puppeteer notification class for webextension	RESOLVED	mozilla56

7 Total; 0 Open (0%); 6 Resolved (85.71%); 1 Verified (14.29%);

* bug 1335456 - (tracking) Path to 57

Full Query

ID	Priority	Component	Assigned to	Summary	Status	Target milestone
1181835	P2	Extension Compatibility	emanuela [ux]	Provide a UI for migrating users' add-ons to webextensions	RESOLVED	---
1214433	P4	Untriaged		[Tracking] Web Extensions Development	RESOLVED	---
1281274	--	Extension Compatibility		Deployment Tracker bug - e10s-addons	RESOLVED	---
1329713	P5	General		[meta] Webextensions Development	RESOLVED	---
1336576	P1	Add-ons Manager		[meta] Limit add-ons loaded into Firefox	RESOLVED	---
1341333	--	Extension Compatibility		Compatibility with Firefox updates	RESOLVED	---
1346460	P1	Extension Compatibility		[meta] Transition support for legacy devs and porting support for Chrome devs	RESOLVED	---
1354344	P3	Preferences	Mark Striemer [:mstriemer]	Show if an extension has set the home page	RESOLVED	mozilla57
1385202	--	Menus		Need a way to manage context menu items.	RESOLVED	---

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

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Installation from AMO
Installation from Discopane
Installation from Add-ons Manager
Installation from Third-party
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 1308292

Bug fix verification

[Verified] Bug 1308309 - Display permissions prompt for webextensions installed using mozAddonManager

↳ 2017-01-10: verified fixed on 53.0a1 across platforms

[Verified] Bug 1308295 - Prompt users with permissions for third-party webextensions installs

↳ 2015-04-21: verified fixed on 53.0a1 across platforms

Logged bugs

Bug 1329942 - 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 link

Merge to Aurora 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
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 Aurora - Full Testing
QA Signoff - Aurora Release		Email to be sent
QA Beta - Full Testing
QA Signoff - Beta Release		Email to be sent