Add-ons/QA/Testplan/Return to AMO

From MozillaWiki
Jump to: navigation, search

Revision History

Date Version Author Description
11/20/2018 1.1 Alexandra Moga / Vlad Jiman / Victor Carciu Created first draft

Note: this document is still under development, some sections may not reflect accurate information on Return to AMO


Overview

This feature aims to redirect a first-time user to install of the extension they've chosen while browsing AMO using a different browser. Currently, if a user installed Firefox in order to get an extension (i.e. Facebook Container, which is unique to Firefox), they are not directed to install the extension during Firstrun

Purpose

This document purports to detail the test approach to Return to AMO, 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
  • The kick-off meeting has taken place

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

Scope

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

what's in scope?

  • Validation of Return to AMO feature.

what's out of scope?

  • Performance testing
  • Security testing

Ownership

Dev Lead: Ursula Sarracini
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Vlad Jiman; irc nick :VladJ
AMO QA: Alexandra Moga; irc nick :LexaSV

Requirements for testing

Environments

OSes covered: Windows, Mac OS X, Linux.

Mobile will not be covered.

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 Reach OnBoarding Tour To verify that OnBoarding Tour can be reached using any browser Manual WebExtensions QA Team
TO-2 Welcome page: Private Browsing To verify that the private browsing feature works as expected from the first welcome screen Manual WebExtensions QA Team
TO-3 Welcome page: Screenshots To verify that the screenshots feature and button works as expected Manual WebExtensions 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 11-04-2018
Study documentation/specs received from developers 11-04-2018
QA - Test plan creation 11-20-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 - Gdocs
  Feature Presentation - Presentation
  

* bug 1468680 - [META] Return to AMO
Full Query
ID Priority Component Assigned to Summary Status Target milestone
1344771 P1 General Shane Caraveo (:mixedpuppy) Desktop attribution on Mac OSX VERIFIED Firefox 63
1472197 -- Security: Review Requests Paul Theriault [:pauljt] (no longer reading bugmail) Security Review: Return-to-AMO RESOLVED Firefox 64
1473017 -- Datasets: General Change datasets to reflect "stub" desktop attribution from OSX installations RESOLVED ---
1475354 P1 Messaging System Ursula Sarracini (:ursula) Create first-run template and content for Return To AMO experience VERIFIED Firefox 65
1476177 P1 Add-ons Manager Andrew Swan [:aswan] Addons with platform specific .xpi files don't end up with a sourceURI attribute VERIFIED mozilla63
1478669 P1 General Shane Caraveo (:mixedpuppy) AddonRepository parsing does not match platform correctly. RESOLVED ---
1486848 P5 Messaging System Return to AMO: if the extension is a Theme - use the paintbrush icon instead of the one from the Theme NEW ---
1501817 P1 Messaging System Ursula Sarracini (:ursula) Create FxA onboarding card VERIFIED Firefox 65
1502501 P1 Messaging System Ursula Sarracini (:ursula) Conditionally show "Return to AMO" instead of StartupOverlay for FxA sign-in on about:welcome VERIFIED Firefox 65
1505189 P2 Messaging System Ursula Sarracini (:ursula) Land Return to AMO Strings RESOLVED Firefox 65
1511071 P1 Messaging System Tim Spurway [:tspurway] QA test plan for Return to AMO RESOLVED ---
1511104 -- Bedrock Paul [:pmac] McLanahan Firefox download page must pass through params, but NOT as utm_ VERIFIED 1.0
1511156 P1 Messaging System Andrei Oprea [:andreio] windows attribution data is double encoded RESOLVED Firefox 66
1511165 P2 Messaging System Andrei Oprea [:andreio] about:welcome addon card on windows says "addon name" VERIFIED Firefox 66
1513317 P1 Messaging System Andrei Oprea [:andreio] Emergency off plan for about:welcome experiences based on site attribution - in this case Return to AMO RESOLVED ---
1513882 P2 Messaging System Punam Dahiya [:pdahiya] about:welcome ReturnToAMO install button does not show the puzzle piece in the awesome bar VERIFIED Firefox 66
1513906 P2 Messaging System Andrei Oprea [:andreio] Polish ReturnToAMO screen VERIFIED Firefox 66
1515153 P1 General Shane Caraveo (:mixedpuppy) accept non-utm params in osx attributions VERIFIED Firefox 66
1515411 P1 Messaging System Andrei Oprea [:andreio] Disable Return to AMO for 65 Beta and Release VERIFIED Firefox 66
1515586 P5 General 'Force Attribution' does not work when using an Firefox browser that is opened inside dmg RESOLVED ---
1517750 P5 Messaging System Invalid width/height on img tag in ReturnToAMO component NEW ---
1519342 P1 Messaging System Andrei Oprea [:andreio] The Onboarding card is displayed immediately after the 'Add to Firefox' button is selected VERIFIED Firefox 66
1519396 P1 Messaging System Andrei Oprea [:andreio] 'Force Attribution' from ASRouter for Return to AMO does not work on Windows VERIFIED Firefox 66
1521501 P3 Messaging System Andrei Oprea [:andreio] Restart browser is required in order to attribute a different extension: Return to AMO RESOLVED ---
1524028 P1 Messaging System Ricky Rosario [:rrosario, :r1cky] Enable ReturnToAMO by default in Beta/Release 66 VERIFIED Firefox 67
1525076 P2 General The nsIMacAttributionService not returning the referrerURL NEW ---
1530816 -- General Shane Caraveo (:mixedpuppy) addonRepository returns emtpy array for rtamo VERIFIED mozilla67
1531713 -- Messaging System RTAMO - about:welcome's 'Install Extension' window should only be shown once RESOLVED ---
1538106 P1 General Andrei Oprea [:andreio] RTAMO about:welcome page is not shown on first run when using a fresh virtual machine RESOLVED ---
1550065 P1 Messaging System Andrei Oprea [:andreio] Add telemetry for Return to AMO experience VERIFIED Firefox 68
1554945 P5 Messaging System Dark theme support for Return-to-AMO screen NEW ---

31 Total; 4 Open (12.9%); 11 Resolved (35.48%); 16 Verified (51.61%);


Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas Covered Details
Reach OnBoarding Tour
Welcome page: Private Browsing
Welcome page: Screenshots

Test suite

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

Bug Work

Tracking bug - Bugzilla

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

Sign off

Criteria

Check list

  • All test cases should be executed
  • 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
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