Add-ons/QA/Testplan/about:addons non-xul rebuild

From MozillaWiki
Jump to: navigation, search

Revision History

Date Version Author Description
02/14/2018 1.0 Cosmin Badescu Created first draft


Overview

  • Building new design and functionality in HTML will allow us to iterate faster, without the burden of dealing with XUL quirks and limitations.
  • It would help to avoid investing deeper in a technology that is deprecated.

Purpose

This document purports to detail the test approach for the improvements of Local Storage API 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
  • 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 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?

  • The XUL interface from about:addons converted to HTML which will iterate faster.

what's out of scope?

  • Security testing

Ownership

Dev Lead: Mark Striemer; irc nick :mstriemer
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Cosmin Badescu; irc nick :CosminB


Requirements for testing

Environments

OSes covered: Windows, Mac OS X, Linux

Channel dependent settings (configs) and environment setups

Nightly

  • Enable extensions.htmlaboutaddons.enabled from about:config

Beta

  • Enable extensions.htmlaboutaddons.enabled from about:config

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 Installing from AMO To verify that the extension uses the API correctly Manual Add-ons QA Team
TO-2 Installing from local files To verify that the extension uses the API correctly Manual Add-ons QA Team
TO-3 Add-on updates To verify that the extension uses the API correctly Manual Add-ons QA Team
TO-4 Sideloading To verify that the extension uses the API correctly 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
QA - Test plan creation 02-14-2018
QA - Test cases/Env preparation 02-13-2018 N/A
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 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 - []
  Install flow - N/A
  


* bug 1505924 - [meta] New about:addons interface
Full Query
ID Priority Component Assigned to Summary Status Resolution Target milestone
1514316 P2 Add-ons Manager Mark Striemer [:mstriemer] Setup a new about:addons behind a pref VERIFIED FIXED mozilla67
1525090 P2 Add-ons Manager Mark Striemer [:mstriemer] Use AddonListeners for HTML about:addons views VERIFIED FIXED mozilla67
1530530 P2 Add-ons Manager Show something when there are no add-ons installed NEW ---
1533795 P1 Add-ons Manager Mark Striemer [:mstriemer] [meta] about:addons interface changes [phase 1] NEW ---
1544111 P3 Themes Tim Nguyen :ntim Fix HTML about:addons to work with dark in-content pages VERIFIED FIXED mozilla68
1546711 P2 Add-ons Manager [about:addons] When aboutaddons.html frame is reloaded, it stays blank until the parent about:addons is reloaded NEW ---
1549450 P2 Add-ons Manager Cleanup inline options browser hacks NEW ---
1550938 -- Add-ons Manager [about:addons] New HTML add-ons manager shows info about extensions in private windows for dictionaries and plugins RESOLVED DUPLICATE ---

8 Total; 4 Open (50%); 1 Resolved (12.5%); 3 Verified (37.5%);


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

Bug Work

Tracking bug - []

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, use template from []


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 02-14-2019
Test Cases Creation 02-13-2019 N/A
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