MozillaWiki

QA/Photon Onboarding Tour Notification

< QA
Revision as of 18:13, 14 August 2017 by Jwilliams7 (talk | contribs) (→‎Test suite)

Revision History

This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded). The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.

Date Version Author Description
06/21/2017 1.0 Justin Williams Created first draft
07/03/2017 1.1 Justin Williams Edits to draft
08/14/2017 1.2 Justin Williams Edits to draft (added V2 information)

Overview

Purpose

Gives a new user/user that has not used Firefox in a while a description and an introduction to Firefox's new innovative features, such as:

  • Private Browsing
  • Addons
  • Customize
  • One-Click Search
  • Default Browser
  • Sync

Scope

Photon Onboarding Tour Notifications will solely focus on the notifications.

Ownership

Engineering lead
  Justin Dolske

Engineering Team
  Fred Lin
  Fischer Liu
  Rex Lee

UX Team: 
  Michael Verdi
  Bryant Mao

QA 
  Justin Williams

Testing summary

Scope of Testing

In Scope

Onboarding Tour Notifications which includes:

  • Private Browsing
  • Addons
  • Customize
  • One-Click Search
  • Default Browser
  • Sync

Out of Scope

Everything not coupled with the Photon Onboarding Tour Notifications is out of scope.

Requirements for testing

Environments

Windows 7 & 10
Ubuntu 17.04
Mac 10.12

Test Strategy

Risk Assessment and Coverage

ID Description / Threat Description Covered by Test Objective Magnitude Probability Priority Impact Score
RAC-1 Tour notification do not get added to the queue if the user does not interact with the notification (tour notification added to queue MAX 8 times or on the 6th day) TO-1 3-High 2-Possible 3-High 18
RAC-2 Tour overlay shows when updating from 55 to 56 (Tour will show for update from 56 to 57) TO-2 3-High 2-Possible 3-High 18
RAC-3 User sees the tour overlay once when updating from 55 to 56 Bug 1377470 TO-2 3-High 2-Possible 3-High 18

Values:

  • Magnitude: 1- Low , 2-Moderate, 3-High
  • Probability: 1-Unlikely, 2-Possible, 3-Almost Certain
  • Priority: 1 - Low, 2-Medium, 3-High

Impact Score Breakdown:

  • An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
  • An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
  • An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.

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 Evaluation Criteria Test Type RAC Owners
1 Do not interact with the tour notification Tour notification gets added to the queue when user does not interact with tour notification (Added to the queue MAX 4 times or on the 6th day) The tour notification successfully gets added to the queue when the user does not interact with the tour notification Manual RAC-1 Eng Team
2 Updating Firefox Updates to Firefox show the tour overlay only when user updates from > 55 to 56. (Tour will show when updating from 56 to 57) The tour notification is not shown when the user updates from 55 to 56. The tour notification is shown when the user updates from 54 to 56 or 56 to 57. Manual RAC-2, RAC-3 Eng Team

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase Start Date End Date
Start project 03/30/1017 11/14/2017
Study documentation/specs received from developers 03/30/2017 08/05/2017
QA - Test plan creation 06/21/2017 11/14/2017
QA - Test cases/Env preparation 07/14/2017 11/14/2017
QA - Nightly Testing V1 07/20/2017 07/25/2017
QA - Beta Testing V1
Release Date V1
QA - Nightly Testing V2 08/18/2017 08/24/2017
QA - Beta Testing V2
Release Date V2 11/14/2017 11/14/2017

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 Onboarding Test Case Creation
Test case execution Onboarding Test Case Execution
Bugs management Notification Meta Bug

Status

Overview

Track the dates and build number where feature was merged to Release/Beta

Channel Date feature was merged to channel Build number
Nightly V1 07/25/2015 20170725030209
Beta V1 08/10/2017 20170810180547
Release V1
Nightly V2
Beta V2
Release V2

References

Testcases

Test Areas

Test Areas Covered Details
Private Window Y have to manually type in about:newtab or about:home
Multi-Process Enabled Y enabled by default which effects majority of the users
Theme (high contrast) Y not all images will be shown bug 1377439
UI
Mouse-only operation Y used by majority of the users
Keyboard-only operation Y accessibility issues are P3 bug 1377300
Display (HiDPI) Y verify that the notifications are shown correctly
Interaction (scroll, zoom) Y effects the tour notifications bug 1381010
Usable with a screen reader Y accessibility issues are P3 bug 1377300
Usability and/or discoverability testing Y
RTL build testing Y rtl issues are P1 bug 1375024
Install/Upgrade
Feature upgrades/downgrades data as expected Y bug 1377470
Does sync work across upgrades Y if user in 56 is in a signed status and updates to 57, we should detect it.
Requires install testing Y stub installer refreshes profile on windows if the user is 2 versions lower than 57 and will not restore the session bug 1369255, bug 1376558
Affects first-run or onboarding Y stub installer refreshes profile on windows if the user is 2 versions lower than 57 and will not restore the session bug 1369255, bug 1376558
Does this affect partner builds? Partner build testing Y browser.onboarding.enabled defaulted on
Data Monitoring
Temporary or permanent telemetry monitoring Y will not be in 56 but may be in 57
Telemetry correctness testing Y will not be in 56 but may be in 57
Interoperability
Interaction of this feature with other browser features Y Private Browsing, Sync

Test suite

Full Test suite - Onboarding Test Suite V1
Full Test suite - Onboarding Test Suite V2

Bug Work

Meta bugs: 1357008 - bug summary

Logged bugs ( blocking 1357008 )
Full Query
ID Priority Component Assigned to Summary Status Target milestone
1357016 P1 General Fischer [:Fischer] Should open the specific tour in the onBoarding overlay when clicking the notification for that specific tour RESOLVED Firefox 57
1357056 P1 General Fischer [:Fischer] Should not display the notification bar if user completed all the tours RESOLVED Firefox 57
1357058 P5 General [meta] Should be able to display tour notification based on the request sent from the back-end server RESOLVED ---
1357641 P1 General Fischer [:Fischer] Should show the notification bar to notify user there is onBoarding tour to learn VERIFIED Firefox 56
1357668 P1 General Verdi [:verdi] Best to slack me [UX] The UX specs for the onBoarding tour notifications VERIFIED Firefox 55
1372067 P1 General Fischer [:Fischer] Should implement the prompt timing policy of the tour notification bar VERIFIED Firefox 56
1409043 P3 Tours [Linux] Onboarding tour highlight is faulty RESOLVED ---

7 Total; 0 Open (0%); 4 Resolved (57.14%); 3 Verified (42.86%);


Bug fix verification
Full Query
ID Priority Component Assigned to Summary Status Resolution Target milestone
1357641 P1 General Fischer [:Fischer] Should show the notification bar to notify user there is onBoarding tour to learn VERIFIED FIXED Firefox 56
1357668 P1 General Verdi [:verdi] Best to slack me [UX] The UX specs for the onBoarding tour notifications VERIFIED FIXED Firefox 55
1372067 P1 General Fischer [:Fischer] Should implement the prompt timing policy of the tour notification bar VERIFIED FIXED Firefox 56

3 Total; 0 Open (0%); 0 Resolved (0%); 3 Verified (100%);

Sign off

Criteria

Checklist

  • 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 V1

List of OSes that will be covered by testing
Win 7 & 10, Ubuntu 16.04, and Mac 10.12


Merge to Beta Sign-off V1

List of OSes that will be covered by testing
Win 7 & 10, Ubuntu 16.04, and Mac 10.12

  • Link for the tests run
    • Full Test suite

Nightly testing V2

List of OSes that will be covered by testing
Win 7 & 10, Ubuntu 16.04, and Mac 10.12


Merge to Beta Sign-off V2

List of OSes that will be covered by testing
Win 7 & 10, Ubuntu 16.04, and Mac 10.12

  • Link for the tests run
    • Full Test suite

Checklist

Exit Criteria Status Notes/Details
Testing Prerequisites (specs, use cases) [DONE] Specs
Testing Infrastructure setup [DONE]
Test Plan Creation [DONE]
Test Cases Creation [DONE]
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
Metrics/Telemetry
Basic/Core functionality Nightly testing
QA mid-Nightly Signoff [DONE] Email Sent
QA Nightly - Full Testing [DONE] Test Results
QA pre-Beta Signoff [DONE] Email Sent
QA Beta - Full Testing
QA pre-Release Signoff Email to be sent
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Photon_Onboarding_Tour_Notification&oldid=1178217"