Revision History

Overview

addons.mozilla.com and accounts.firefox.com were moved into a new process type to close out sandbox escape vectors.

Purpose

Because these APIs can allow sandbox escapes.

Entry Criteria

• QA has access to PRD
• Firefox Release Train: Fx70, manual testing required in Beta

Current Status

• The test cases are created and waiting for Beta 70

Exit Criteria

• All blockers fixed
• All resolved bugs verified by QA

Scope

what's in scope?

• Install and Uninstall of add-ons from AMO pages
• Disabling add-ons from Addon Manager and Enable them from AMO detail pages

what's out of scope?

• Add-ons/Webextensions functionality

Ownership

Product Manager: Jorge Villalobos; irc nick :jorgev
Engineering Manager: Stuart Colville; irc nick :muffinresearch
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: Ioana Rusiczki; irc nick :ioanaR

Requirements for testing

Environments

• Windows
• Mac OS
• Linux

Testing Environments

• Production: https://addons.mozilla.org/en-US/
• Addon Manager: about:addons

Channels

• Beta

Test Strategy

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Created a doc with more detailed scenarios - Restrict Legacy Add-ons Submission

Testing Tools

References

* PRD - https://docs.google.com/document/d/1bfSlCl5gI7-2H9IeoVQ1KW5v3gADZ7cuWofdL7GC7-E/edit
* Tracker: not available yet

Bug Work

• Meta bug - 1539595

Sign off

Criteria

Check list

• All test cases should be executed
• All blockers must be fixed and verified or have an agreed-upon timeline for being fixed