View source for QA/Send install Firefox link via SMS

'''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.

{| class="wikitable" style="width:60%"
|-
! 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 <br/>

== Ownership ==
'''Mozilla Development''' <br />
Shane Tomlinson - [mailto:stomlinson@mozilla.com]<br />

'''QA Eng. Softvision Las Vegas''' <br />
PM for QA team - [mailto:rares.bologa@softvisioninc.eu Rares Bologa] (IRC: RaresB)<br />
QA Lead- [mailto:kkumari@softvision.com Kanchan Kumari] (IRC: Kanchan_QA)<br />
QA - [mailto:gwimberly@softvision.com Grover Wimberly IV] (IRC: Grover-QA)<br />
QA - [mailto:amasresha@softvision.com Abe Masresha] (IRC: Abe_LV)<br />
QA - [mailto:stefan.georgiev@softvision.com Stefan Georgiev] (IRC: StefanG_QA)<br />
QA - [mailto:jwilliams@softvision.com Justin Williams] (IRC: JW_SoftvisionQA)<br />

= 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 - 
* Links for Nightly builds https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/

== Test Execution Schedule ==
The following table identifies the anticipated testing period available for test execution.
{| class="wikitable" style="width:60%"
|-
! Project phase !! Start Date !! End Date
|-
| Start project 
|style="text-align:center;" |  || 
|-
| Study documentation/specs received from developers
|style="text-align:center;" | 02/27/2017 || 
|-
| QA - Test plan creation 
|style="text-align:center;" |  02/27/2017|| 
|-
| QA - Test cases/Env preparation 
|style="text-align:center;" | TBD|| 
|-
| QA - Nightly Testing 
|style="text-align:center;" | TBD || 
|-

| Release Date 
|style="text-align:center;" | TBD || 
|}

== Testing Tools ==
Detail the tools to be used for testing, for example see the following table:
{| class="wikitable" style="width:50%"
|-
! Process !! Tool
|-
| Test plan creation || Mozilla wiki
|-
| Test case creation || [https://testrail.stage.mozaws.net/index.php TestRail]/ Google docs
|-
| Test case execution || [https://testrail.stage.mozaws.net/index.php TestRail]
|-
| Bugs management || Bugzilla
|}

= Status = 
== Overview ==

= References =

= Testcases = 
== Overview ==

Summary of testing scenarios

== Test Areas ==
{| class="wikitable" style="width:80%"
|-
! Test Areas !! Covered !! Details
|-
| Private Window 
|style="text-align:center;" | Yes|| 
|-
| Multi-Process Enabled 
|style="text-align:center;" | Yes || 
|-
| Multi-process Disabled 
|style="text-align:center;" | Yes || 
|-
| Does sync work across upgrades   
|style="text-align:center;" | Yes || 
|-

| ''' Interoperability  ''' 
||  || depends on the feature

|-
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS
|style="text-align:center;" |  Yes|| 
|-
| Interaction of this feature with other browser features   
|style="text-align:center;" | Yes || 
|}

== Test suite ==
 Full Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1N8dGK_uenhfcM9cEPC3HPHmi0jFN98FWtL2DuszrfLY/edit#gid=0 link]
 Smoke Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1N8dGK_uenhfcM9cEPC3HPHmi0jFN98FWtL2DuszrfLY/edit#gid=0 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'''<br />

List of OSes that will be covered by testing<br />
*Link for the tests run
** Daily Smoke, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Full Test suite, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Regression Test suite, if needed/available

'''Merge to Aurora Sign-off'''
List of OSes that will be covered by testing<br />
*Link for the tests run
** Full Test suite

== Checklist ==
{| class="wikitable" style="width:60%"
|-
! Exit Criteria !! Status !! Notes/Details
|-
|  Testing Prerequisites (specs, use cases) 
| style="text-align:center;" | Done
| style="text-align:center;" | 
|-
|  Testing Infrastructure setup 
|style="text-align:center;" | TBD  || 
|-
|  Test Plan Creation 
| style="text-align:center;" | Done  || 
|-
|  Test Cases Creation 
|style="text-align:center;" |  TBD || 
|-
|  Full Functional Tests Execution 
|style="text-align:center;" |  TBD
|style="text-align:center;" |  
|-
|  Automation Coverage 
|style="text-align:center;" | NA ||
|-
|  Performance Testing 
|style="text-align:center;" |  NA || 
|-
|  All Defects Logged 
|style="text-align:center;" | TBD  || 
|-
|  Critical/Blockers Fixed and Verified 
|style="text-align:center;" | TBD || 
|-
|  Metrics/Telemetry|| 
|style="text-align:center;" | 
|-
|  QA Signoff  - Nightly Release|| 
|style="text-align:center;" | Email to be sent 
|-
|  QA Aurora - Full Testing 
|style="text-align:center;" |  || 
|-
|  QA Signoff  - Aurora Release || 
|style="text-align:center;"| Email to be sent 
|-
|  QA Beta - Full Testing
|style="text-align:center;" |  || 
|-
|  QA Signoff  - Beta Release || 
|style="text-align:center;" | Email to be sent 
|}