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
04/28/2017	1.0	Kanchan Kumari	Created first draft

Overview

Purpose

Purpose is to test the "Secondary Email"feature for Firefox account

Ownership

Mozilla Development
Vijay Budhram - [1]

QA Eng. Softvision Las Vegas
QA - Kanchan Kumari (IRC: Kanchan_QA)

Testing summary

Scope of Testing

In Scope

The testing effort will be focused on the following areas:

• Firefox account new UI with Secondary Email.
• Functionality of buttons like Add, Done, remove, refresh etc related to Secondary Email field.
• Failures conditions related availability/unavailability of secondary email ids.
• Positive Scenario - Secondary email gets added for all the valid criteria.
• Login notification, Password reset email, verification link, secondary email confirmation message, verified/unverified email states, etc.
• Testing of the secondary email feature to be executed on multiple devices including desktop, Android and iOS.
• Regression testing involving the current account confirmation process, UI elements, etc.

All the above areas will be tested manually.

Out of Scope

Automation will be handled by the developer (if needed)

Requirements for testing

Environments

Windows, Mac OS, Linux, Android, iOS

Risk Analysis

Ensure this new feature doesn't break current account confirmation process, UI elements etc.

Test Strategy

Test Objectives

Through this verification effort, aim is to achieve following test objectives:

• Verify that new UI items like secondary email field, add, change, remove, refresh, done etc.
• Verify that Secondary Email can be associated to an FxA now.
• Verify that secondary email doesn't get added to Firefox account which has unverified primary email.
• Verify that secondary email field doesn't accept the verified primary email address of same/different Firefox account.
• Verify that secondary email doesn't get added to Firefox account with unverified primary email on existing Firefox account which is <1 day old.
• Verify that unverified primary email (on existing Firefox account which is >1 day old) gets added as secondary email to Firefox account.
• Verify that secondary email field doesn't accept the verified secondary email address of other Firefox account.
• Verify that secondary email gets created with the unverified secondary email of other existing account.
• Verify that new Firefox account doesn't get created with secondary email of existing fx account.
• Verify that primary email gets notification for added secondary email.
• Verify that primary and secondary emails of deleted Fx account is available to use for other Fx account.
• Verify that both primary and secobdary emails get password reset link/ password change notification.
• Verify that sign-in unblock code is sent to both verified primary and secondary emails.
• Verify that sign-in confirmation email is dent to both verified primary and secondary emails.
• Verify that this feature works correctly on any platform, desktop (Windows, Linux, Mac), Android or iOS.
• Verify that it doesn't break the existing account confirmation process, UI elements through regression testing.

Builds

This section should contain links for builds with the feature -

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	04/25/2017
QA - Test plan creation	04/28/2017
QA - Test cases/Env preparation	04/28/2017
QA -Testing	TBD
Release Date	TBD

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	TestRail/ Google docs
Test case execution	TestRail
Bugs management	Bugzilla

Status

Overview

References

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Private Window	Yes
Multi-Process Enabled	Yes
Multi-process Disabled	Yes
Does sync work across upgrades	Yes
Interoperability		depends on the feature
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS	Yes
Interaction of this feature with other browser features	Yes

Test suite

Full Test suite - Link with the gdoc, follow the format from link
Smoke Test suite - Link with the gdoc, follow the format from link
Regression Test suite - Link with the gdoc - if available/needed.

Bug Work

Open Bugs
1362218
1363545
1363470
1362513
1362190 (Not related to Secondary Email feature)
1362589 (Resolved-Fixed)

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 and critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)

Results

Tested on Custom Test Environment

Test Suit

Test Run

Test Report

Checklist

Exit Criteria	Status	Notes/Details
Testing Prerequisites (specs, use cases)	Done
Testing Infrastructure setup	Done
Test Plan Creation	Done
Test Cases Creation	Done
Full Functional Tests Execution	Done
Automation Coverage	NA
Performance Testing	NA
All Defects Logged	Done
Critical/Blockers Fixed and Verified	Done
Metrics/Telemetry
QA Signoff - Custom Test Environment		Email sent