Revision History

Date	Version	Author	Description
10/08/2018	1.0	Alexandra Gal-Moga	Created first draft

Overview

The purpose of this feature is to help users understand how they are being tracked and targeted with ads on Facebook. The addon parses ad information displayed on Facebook pages in the browser and displays them a sidebar with context added from an included dataset.

Purpose

This document will detail the test approach for the Facebook Monitor extension functionality 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
• QA has access to the finalized extension repository

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

Scope

This section describes what parts of the feature will be tested and what parts won't be.

what's in scope?

• add-on validation and submission through AMO Developer Hub
• add-on installation from its listing page on AMO
• extension functionality after installation.

what's out of scope?

• Security testing

Ownership

Dev Lead: Jason Chuang; irc nick :jchuang
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Cosmin Badescu; irc nick :CosminB
Webextensions QA: Alexandra Gal-Moga; irc nick :LexaSV

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	Submission in AMO	Checks that add-on is validated and submitted in Dev Hub	Manual	Add-ons QA Team
TO-2	Installing from AMO	To verify that the extension installs correctly	Manual	Add-ons QA Team
TO-3	Installing from local files	To verify that the extension installs correctly	Manual	Add-ons QA Team
TO-4	Add-on updates	To verify that the extension updates correctly	Manual	Add-ons QA Team
TO-5	Sideloading	To verify that the extension installs correctly	Manual	Add-ons QA Team

Builds

This section should contain links for builds with the extension-

• Link for add-on repository in GitHub

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	10-08-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 of the extension released for testing

Risk analysis

Identify the high-risk assumptions
Identify existing bugs on the feature with high risk

References

* List and links for specs
  Test Plan - TBD
  Repository - Link   

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Installing from AMO
Installing from local files
Installing from thirdparty
Add-on updates
Sideloading
Submission in AMO

Test suite

• Link for the [ Initial test planning]
• Link for the [ Google doc tests - TBD]

Bug Work

Tracking bug - []