Add-ons/QA/Testplan/Roll disco pane into about:addons: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "TBD")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
TBD
'''Revision History'''
 
{| class="wikitable" style="width:60%"
|-
! Date !! Version !! Author !! Description
|-
| 04/15/2018 || 1.0 || Cosmin Badescu || Created first draft
|-
|}
 
 
= Overview =
 
*The discovery pane of about:addons is actually an AMO web page that is styled to look like it is part of about:addons. Since disco pane is part of the Add-on Manager experience, it should be integrated for efficiency and consistency.
 
== 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?===
* With the re-write of about:addons into HTML and changes to telemetry in disco pane, now is the time to integrate them so we can finally have them under one roof and avoid a disruption to disco pane’s telemetry. Furthermore, AMO and Firefox have different release cycles, making it difficult to keep disco pane and about:addons consistent.
 
===what's out of scope?===
* Security testing
 
== Ownership ==
Dev Lead: [mailto:mstriemer@mozilla.com Mark Striemer]; irc nick :mstriemer <br />
Dev Lead: [mailto:rwu@mozilla.com Rob Wu]; irc nick :robwu_nl <br />
QA Manager: [mailto:kraj@mozilla.com Krupa Raj]; irc nick :krupa<br />
QA Lead: [mailto:vcarciu@softvision.ro Victor Carciu]; irc nick :victorc<br />
Webextensions QA: [mailto:cosmin.badescu@softvision.ro Cosmin Badescu]; irc nick :CosminB<br />
 
 
= Requirements for testing =
== Environments ==
OSes covered: Windows, Mac OS X, Linux
 
== Channel dependent settings (configs) and environment setups ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
 
=== Nightly ===
<div class="mw-collapsible-content">
*N/A
</div>
 
=== Beta ===
<div class="mw-collapsible-content">
*N/A
</div>
 
=== Release ===
<div class="mw-collapsible-content">
The feature is enabled by default
</div>
</div>
 
= 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.
 
{| class="wikitable"
|-
! Ref !! Function !! Test Objective !! Test Type !! Owners
|-
| TO-1 || Card changed to the new format || To verify that the extensions card are displayed correctly || Manual || Add-ons QA Team
|-
| TO-2 || Recommended section || To verify that the transition from "Get Add-ons" section to the "Recommended" section is working properly || Manual || Add-ons QA Team
|-
|}
 
== Builds ==
This section should contain links for builds with the feature -
* [http://archive.mozilla.org/pub/mobile/nightly/latest-date-android-api-16/ Link] for Nightly builds
* [http://archive.mozilla.org/pub/mobile/candidates/ Link] for Beta builds
* [http://archive.mozilla.org/pub/mobile/releases/ Link] for Release builds
 
== Test Execution Schedule ==
The following table identifies the anticipated testing period available for test execution.
{| class="wikitable" style="width:60%"
|-
! Project phase !! Start Date !! End Date
|-
| Start project
|style="text-align:center;" |  ||
|-
| Study documentation/specs received from developers
|style="text-align:center;" |  ||
|-
| QA - Test plan creation
|style="text-align:center;" | 04-15-2018 ||
|-
| QA - Test cases/Env preparation
|style="text-align:center;" | ||
|-
| QA - Nightly Testing
|style="text-align:center;" |  ||
|-
| QA - Beta Testing
|style="text-align:center;" |  ||
|-
| Release Date
|style="text-align:center;" | ||
|}
 
== Testing Tools ==
Detail the tools to be used for testing, for example see the following table:
{| class="wikitable" style="width:50%"
|-
! 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 - [https://docs.google.com/document/d/1_0FXaXkDSb2FSD_ZYE_SlOlZNR4cnIrmqHJuqz9ud-c/edit# Gdoc]
  Feature flow - [N/A]
 
 
 
* {{Bug|1540173}} - [meta] change "Get Add-ons" (discopane) to be a proper part of about:addons rather than a framed page from AMO
<bugzilla>
    {
        "blocks":[1540173],
        "include_fields": "id, priority, component, assigned_to, summary, status, resolution, target_milestone"
    }
</bugzilla>
 
= Testcases =
== Overview ==
Summary of testing scenarios
== Test Areas ==
{| class="wikitable" style="width:80%"
|-
! Test Areas !! Covered !! Details
|-
| '''Installing from AMO'''
|style="text-align:center;" | ||
|-
| '''Installing from local files'''
|style="text-align:center;" |  ||
|-
| '''Installing from thirdparty'''
|style="text-align:center;" |  ||
|-
| '''Add-on updates'''
|style="text-align:center;" |  ||
|-
| '''Sideloading'''
||  ||
|-
| '''Other''' 
|style="text-align:center;" |  ||
|-
|}
 
== Test suite ==
* Link for the [ Initial test planning]
* Link for the [ Google doc tests]
* Link for the [ Test rail Roll disco pane into about:addons]
 
 
= Bug Work =
Tracking bug - []
 
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
 
====== Bug fix verification ======
<div class="mw-collapsible-content">
<font color="green">'''[Verified]'''</font> [ Bug xxxxxxx] - Display permissions prompt for webextensions installed using mozAddonManager
:↳ <small>'''2017-01-10'''</small>: verified fixed on 53.0a1 across platforms
<font color="green">'''[Verified]'''</font> [ Bug xxxxxxx] - Prompt users with permissions for third-party webextensions installs
:↳ <small>'''2015-04-21'''</small>: verified fixed on 53.0a1 across platforms
</div></div>
 
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
 
====== Logged bugs ======
<div class="mw-collapsible-content">
[ Bug xxxxxxx] - Misaligned icon and webextension name in permissions doorhanger<br/>
 
</div>
</div>
 
= 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, critical must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)
 
== Results ==
'''Nightly testing'''<br />
 
List of OSes that will be covered by testing<br />
*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<br />
*Link for the tests run
** Full Test suite
 
== Checklist ==
{| class="wikitable" style="width:60%"
|-
! Exit Criteria !! Status !! Notes/Details
|-
|  Testing Prerequisites (specs, use cases)
| style="text-align:center;" | 
| style="text-align:center;" |
|-
|  Testing Infrastructure setup
|style="text-align:center;" |  ||
|-
|  Test Plan Creation
| style="text-align:center;" | 04-15-2019  ||
|-
|  Test Cases Creation
|style="text-align:center;" |  ||
|-
|  Full Functional Tests Execution
|style="text-align:center;" | 
|style="text-align:center;" | 
|-
|  Automation Coverage ||
|style="text-align:center;" |
|-
|  Performance Testing
|style="text-align:center;" |  ||
|-
|  All Defects Logged || ||
|-
|  Critical/Blockers Fixed and Verified || ||
|-
|  Metrics/Telemetry||
|style="text-align:center;" |
|-
|  QA Signoff  - Nightly Release||
|style="text-align:center;" |
|-
|  QA Beta - Full Testing
|style="text-align:center;" |  ||
|-
|  QA Signoff  - Beta Release ||
|style="text-align:center;" | Email to be sent
|}

Latest revision as of 09:16, 18 April 2019

Revision History

Date Version Author Description
04/15/2018 1.0 Cosmin Badescu Created first draft


Overview

  • The discovery pane of about:addons is actually an AMO web page that is styled to look like it is part of about:addons. Since disco pane is part of the Add-on Manager experience, it should be integrated for efficiency and consistency.

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?

  • With the re-write of about:addons into HTML and changes to telemetry in disco pane, now is the time to integrate them so we can finally have them under one roof and avoid a disruption to disco pane’s telemetry. Furthermore, AMO and Firefox have different release cycles, making it difficult to keep disco pane and about:addons consistent.

what's out of scope?

  • Security testing

Ownership

Dev Lead: Mark Striemer; irc nick :mstriemer
Dev Lead: Rob Wu; irc nick :robwu_nl
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

  • N/A

Beta

  • N/A

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 Card changed to the new format To verify that the extensions card are displayed correctly Manual Add-ons QA Team
TO-2 Recommended section To verify that the transition from "Get Add-ons" section to the "Recommended" section is working properly 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 04-15-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 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 - Gdoc
  Feature flow - [N/A]
  



* bug 1540173 - [meta] change "Get Add-ons" (discopane) to be a proper part of about:addons rather than a framed page from AMO
Full Query
ID Priority Component Assigned to Summary Status Resolution Target milestone
1539598 P1 Add-ons Manager Andrew Swan [:aswan] Restrict mozAddonManager's special privileges to calls from the discovery pane VERIFIED FIXED mozilla68
1542262 P2 Add-ons Manager Rob Wu [:robwu] Match star rating icons to AMO VERIFIED FIXED mozilla68
1546123 P1 Add-ons Manager Rob Wu [:robwu] [about:addons] Fix size detection for preview images VERIFIED FIXED mozilla68
1546248 P1 Add-ons Manager Rob Wu [:robwu] [about:addons] Create in-tree discopane to replace the remotely hosted discopane VERIFIED FIXED mozilla68
1546980 P1 Add-ons Manager Rob Wu [:robwu] [about:addons] Add ratings and user counts to discopane VERIFIED FIXED mozilla68
1548383 P2 Add-ons Manager Rob Wu [:robwu] [about:addons] Support extensions.getAddons.showPane pref to disable HTML-based discopane VERIFIED FIXED mozilla68
1558183 -- Add-ons Manager Prompt displayed before install in about:addons RESOLVED INVALID ---

7 Total; 0 Open (0%); 1 Resolved (14.29%); 6 Verified (85.71%);


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 [ Initial test planning]
  • Link for the [ Google doc tests]
  • Link for the [ Test rail Roll disco pane into about:addons]


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, critical 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 04-15-2019
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
QA Beta - Full Testing
QA Signoff - Beta Release Email to be sent
Retrieved from "https://wiki.mozilla.org/index.php?title=Add-ons/QA/Testplan/Roll_disco_pane_into_about:addons&oldid=1210843"