Add-ons/QA/Testplan/declarativeContent API

Revision History

Date	Version	Author	Description
10/23/2018	1.0	Vlad Jiman	Created first draft

Please note, this document is still under development and parts have not been modified from the template cloning, other sections are placeholders

Overview

Purpose

This document purports to detail the test approach to declarativeContent API and including 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
• 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 out of scope?

• Performance testing
• Security testing

Ownership

Dev Lead: Rob Wu ; irc nick:robwu_nl
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Vlad Jiman; irc nick :VladJ

Requirements for testing

Environments

OSes covered: Windows, Mac OS X, Linux, Mobile (TBD)

Channel dependent settings (configs) and environment setups

Nightly

security.signed_app_signatures.policy with the default value 2

Beta

security.signed_app_signatures.policy with the default value 2

Release

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	Test Type	Owners
TO-1	Match using URL	To verify that the extension will correctly hide its icon when matching by URL	Manual	Add-ons QA Team
TO-2	Match using CSS	To verify that the extension will correctly hide its icon when matching by CSS	Manual	Add-ons QA Team
TO-3	Match using CSS + URL	To verify that the extension will correctly hide its icon when matching by CSS + URL	Manual	Add-ons QA Team
TO-4	Browser restart/crash scenarios	To verify that the extension will correctly work in previous scenarios ever after restart/crash	Manual	Add-ons QA Team
TO-5	Sideloading, Debug	To verify that the extension will correctly work after being loaded by sideload or as temporary addon	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	10/23/2018
QA - Test plan creation	10/23/2018
QA - Test cases/Env preparation	10/25/2018
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	[ 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 - chromeDev
    

* bug 1435864 - [META] Implement declarativeContent API

Full Query

ID	Priority	Component	Assigned to	Summary	Status	Target milestone
1315829	P2	General	Rob Wu [:robwu]	Intermittent TEST-UNEXPECTED-TIMEOUT | toolkit/components/extensions/test/xpcshell/test_ext_runtime_onInstalled_and_onStartup.js | Test timed out	RESOLVED	mozilla66
1323433	P2	General		Implement a declarative content script API	RESOLVED	---
1432647	P5	General		Support themes with declarativeContent API	REOPENED	---
1465994	P5	General		Implement setIcon as declarativeContent API	NEW	---
1465995	P5	General		Implement ShowPageAction for declarativeContent API	NEW	---
1540215	P5	General	Rob Wu [:robwu]	Implement declarativeContent.IgnoreRules action	RESOLVED	---

6 Total; 3 Open (50%); 3 Resolved (50%); 0 Verified (0%);

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
Other

Test suite

• Link for the [ TestRail]

Bug Work

Tracking bug - [1435864]

Bug fix verification

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

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

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

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

Logged bugs

[ Bug xxxxxxx] - 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

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	10/23/2018
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 Beta - Full Testing
QA Signoff - Beta Release		Email to be sent