Add-ons/QA/Testplan/AMO Process Isolation

From MozillaWiki
Jump to: navigation, search

Revision History

Date Version Author Description
30/08/2019 1.0 Ioana Rusiczki Created first draft

Overview and were moved into a new process type to close out sandbox escape vectors.


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


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


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


  • Windows
  • Mac OS
  • Linux

Testing Environments


  • Beta

Test Strategy

Test Execution Schedule

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

Project phase Start Date End Date
Start project 15.06.2019
Study PRD/mocks received 15.06.2019
QA - Test plan creation 30.08.2019
QA - Test cases preparation 30.08.2019
QA - Test cases execution
Release Date 22.10.2019 (Firefox Release 70)

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

Testing Tools

Process Tool
Test plan creation Mozilla wiki
Test case creation TestRail
Bugs management Bugzilla


* PRD -
* Tracker: not available yet

Bug Work

Bug fix verification
Logged bugs

Sign off


Check list

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