QA/Send install Firefox link via SMS

From MozillaWiki
< QA
Jump to: navigation, search

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

Overview

Purpose

Purpose is to test the "Send install Firefox link via SMS" feature

Ownership

Mozilla Development
Shane Tomlinson - [1]

QA Eng. Softvision Las Vegas
PM for QA team - Rares Bologa (IRC: RaresB)
QA Lead- Kanchan Kumari (IRC: Kanchan_QA)
QA - Grover Wimberly IV (IRC: Grover-QA)
QA - Abe Masresha (IRC: Abe_LV)
QA - Stefan Georgiev (IRC: StefanG_QA)
QA - Justin Williams (IRC: JW_SoftvisionQA)

Testing summary

Scope of Testing

In Scope

The testing effort will be focused on the following areas:

  • New UI items like mobile number field, Learn More, May Be later, etc.
  • Tests for validation of mobile number field (including invalid phone number, multiple phone numbers, error returned by the server, etc.)
  • Limiting the number of SMS that can be sent from a specific FX account.
  • Ensure that user gets the installer link through SMS on mobile on successful data post.
  • SMS link should take the user to the Google Play Store/ Apple Store.
  • Testing for the new mobile number feature to be executed on multiple devices including desktop, Android and iOS.
  • SMS can be received only in EN countries (USA, Canada & UK), not any other country.
  • 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 mobile number field, "Learn More", "May Be later", etc. are displayed/behave as per the specifications.
  • Verify that the new mobile number field passes validation tests involving invalid phone number, error returned from the server, etc. as per the specifications.
  • Verify that user is throttled from sending SMSs if they send 5 messages within the span of an hour.
  • Verify that user receives the link through SMS on specified number on succseful phone information submission. Verify that content of the SMS is as per the specification.
  • verify that SMS link should take the user to the Google Play Store/ Apple Store corresponding to the device.
  • 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 02/27/2017
QA - Test plan creation 02/27/2017
QA - Test cases/Env preparation TBD
QA - Nightly 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

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

Nightly testing

List of OSes that will be covered by testing

  • Link for the tests run
    • Daily Smoke, use template from link
    • Full Test suite, use template from link
    • Regression Test suite, if needed/available

Merge to Aurora 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) Done
Testing Infrastructure setup TBD
Test Plan Creation Done
Test Cases Creation TBD
Full Functional Tests Execution TBD
Automation Coverage NA
Performance Testing NA
All Defects Logged TBD
Critical/Blockers Fixed and Verified TBD
Metrics/Telemetry
QA Signoff - Nightly Release Email to be sent
QA Aurora - Full Testing
QA Signoff - Aurora Release Email to be sent
QA Beta - Full Testing
QA Signoff - Beta Release Email to be sent
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Send_install_Firefox_link_via_SMS&oldid=1164044"