QA/Photon Onboarding Tour Notification
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) |
Contents
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:
V1 New User
- Private Browsing
- Addons
- Customize
- One-Click Search
- Default Browser
- Sync
V2 New User
- Performance
- Private Browsing
- Screenshots
- Add-ons
- Customize
- Default Browser
V2 Updated User
- Performance
- Library
- Screenshots
- Search
- Customize
- Sync
with a notification that is accessed by opening the about:newtab page or the default about:home page.
Ownership
Engineering lead Tim Chien
Engineering Team Fred Lin Fischer Liu Rex Lee
UX Team: Michael Verdi Bryant Mao
QA Justin Williams
Testing summary
Scope of Testing
In Scope
1. Profile Refresh.
2. Onboarding Tour Notifications which includes:
V1 New User
- Private Browsing
- Addons
- Customize
- One-Click Search
- Default Browser
- Sync
V2 New User
- Performance
- Private Browsing
- Screenshots
- Add-ons
- Customize
- Default Browser
V2 Updated User
- Performance
- Library
- Screenshots
- Search
- Customize
- Sync
These notifications are shown to give the user a walk through/introduction of the above features.
Out of Scope
Everything that does not include the features in scope, about:newtab, about:home, profile refresh and the hamburger menu. Fennec is also out of scope.
Requirements for testing
Environments
Windows 7 x64: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz Windows 10 x64: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz, 3601 Mhz Ubuntu 17.04 x64:Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz Mac 10.12 x64: 2.7 GHz Intel Core i5
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 if ignored 8 impressions of the notification or on the 6th day) | TO-1 | 3-High | 2-Possible | 3-High | 18 |
| RAC-2 | Tour notification shows when updating from 55 to 56 | TO-2 | 3-High | 2-Possible | 3-High | 18 |
| RAC-3 | Currently no automation test coverage | 3-High | 2-Possible | 2-Medium | 12 |
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 | The tour notification successfully gets added to the queue when the user does 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) | Manual | RAC-1 | Eng Team |
| 2 | Updating Firefox | Updates to Firefox show the tour notifications only when user updates from a version lower than 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 | Eng Team |
| 3 | Total tour notification timeout | Tour notifications get finished automatically for users who really seldom uses Firefox (not use for over 14 day) | After the 1st seeing of one tour notification then without using Firefox more than 14 days, no more notification is shown. | Manual | RAC-1 | 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 V1 | Onboarding Test Case Creation V1 |
| Test case execution V1 | Onboarding Test Case Execution V1 |
| Test case creation V2 | Onboarding Test Case Creation V2 |
| Test case execution V2 | Onboarding Test Case Execution V2 |
| Bugs management | Notification Meta Bug |
| Trello Card | Notifications Trello Card |
| Specs V1 | Notifications V1 Specs |
| Specs V2 | Notifications V2 Specs |
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/2017 | 20170725030209 |
| Beta V1 | 08/10/2017 | 20170810180547 |
| Release V1 | ||
| Nightly V2 | 08/18/2017 | 20170818100226 |
| Beta V2 | ||
| Release V2 |
Testcases
Test Areas
| Test Areas | Covered | Details | Reviewed by |
|---|---|---|---|
| Private Window | Y | have to manually type in about:newtab or about:home | TPE Eng Team |
| Multi-Process Enabled | Y | enabled by default which effects majority of the users | TPE Eng Team |
| Theme (high contrast) | Y | not all images will be shown bug 1377439 | TPE Eng Team |
| UI | |||
| Mouse-only operation | Y | used by majority of the users | TPE Eng Team |
| Keyboard-only operation | Y | accessibility issues are P3 bug 1377300 | TPE Eng Team |
| Display (HiDPI) | Y | verify that the notifications are shown correctly | TPE Eng Team |
| Interaction (scroll, zoom) | Y | effects the tour notifications bug 1381010 | TPE Eng Team |
| Usable with a screen reader | Y | accessibility issues are P3 bug 1377300 | TPE Eng Team |
| Usability and/or discoverability testing | Y | Verify that the product is user friendly | TPE Eng Team |
| RTL build testing | Y | rtl issues are P1 bug 1375024 | TPE Eng Team |
| Install/Upgrade | |||
| Feature upgrades/downgrades data as expected | Y | bug 1377470 | TPE Eng Team |
| Does sync work across upgrades | Y | if user in 56 is in a signed status and updates to 57, we should detect it. | TPE Eng Team |
| 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 | TPE Eng Team |
| 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 | TPE Eng Team |
| Does this affect partner builds? Partner build testing | Y | browser.onboarding.enabled defaulted on | TPE Eng Team |
| Data Monitoring | |||
| Temporary or permanent telemetry monitoring | Y | will not be in 56 but may be in 57 | TPE Eng Team |
| Telemetry correctness testing | Y | will not be in 56 but may be in 57 | TPE Eng Team |
| Interoperability | |||
| Interaction of this feature with other browser features | Y | Private Browsing, Sync | TPE Eng Team |
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
- Link for the tests run
- Full Test suite, link to TestRail - Tests Runs and Results Onboarding Test Run V1
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
- Link for the tests run
- Full Test suite, link to TestRail - Tests Runs and Results Onboarding Test Run V2
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 | N/A | |
| Performance Testing | N/A | |
| All Defects Logged | IN PROGRESS | |
| Critical/Blockers Fixed and Verified | IN PROGRESS | |
| Metrics/Telemetry | IN PROGRESS | |
| Basic/Core functionality Nightly testing V1 | [DONE] | |
| QA mid-Nightly Signoff V1 | [DONE] | Email Sent |
| QA Nightly - Full Testing V1 | [DONE] | Test Results |
| QA pre-Beta Signoff V1 | [DONE] | Email Sent |
| QA Beta - Full Testing V1 | ||
| QA pre-Release Signoff V1 | Email to be sent | |
| Basic/Core functionality Nightly testing V2 | IN PROGRESS | |
| QA mid-Nightly Signoff V2 | [DONE] | Email sent |
| QA Nightly - Full Testing V2 | ||
| QA pre-Beta Signoff V2 | Email to be sent | |
| QA Beta - Full Testing V2 | ||
| QA pre-Release Signoff V2 | Email to be sent |
Approvals Required / Received
The following individuals are required to/have approved this Test Plan:
| Name | Title | Department | Approval Date | Method |
|---|---|---|---|---|
| Lawrence Mandel / RyanVM | QA Reviewer | Product Integrity | ||
| Tim Chien | Software Engineer | Engineering | 09/06/2017 | |
| Cindy Hsiang | PM | Product Management | 09/07/2017 |
