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
05/01/2017	1.0	Cornel Ionce	Created first draft

Overview

Purpose

Detail the purpose of this document. For example:

• The test scope, focus areas and objectives
• The test responsibilities
• The test strategy for the levels and types of test for this release
• The entry and exit criteria
• The basis of the test estimates
• Any risks, issues, assumptions and test dependencies
• The test schedule and major milestones
• The test deliverables

Scope

This wiki details the testing that will be performed by the project team for the DTMF support in Firefox. Its purpose is to document:

• What will be tested
• How testing will be performed

Ownership

Engineering contacts: Daniel Minor, :dminor on IRC

QA Lead: Cornel Ionce, :cornel_ionce on IRC QA: Iulia Cristescu, :IuliaC on IRC

Testing summary

Scope of Testing

In Scope

DTMF support in Firefox is planned to be shipped with Firefox 52 and it's enabled by default. This feature ensures the usage of WebRTC dual-tone multi-frequency signaling is working in Firefox.

The testing efforts will be invested on the following areas:

• functionality:
• performance:
• accessibility:

Out of Scope

• (note that this area is currently under assessment and the information here is not final)
• Since this feature does not have any kind of UI exposed, there will be no testing conducted with UI in mind.

Requirements for testing

Environments

Full Testing will be performed on:

• Windows 7
• Windows 10
• Ubuntu 12.04
• Ubuntu 16.04
• Mac OS X 10.9.5
• Mac OS X 10.12

Exploratory/Smoke testing will be performed on

• Windows 7
• Windows 10
• Ubuntu 16.04
• Mac OS X 10.12

Specify other configuration/environmental setup needed:

• none

Test Strategy

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	Owners
1
2
3
4
5
6

Builds

This section should contain links for builds with the feature:

• Links for Nightly builds
• Links for Aurora builds
• Links for Beta builds - will only be available on Beta 52.

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
QA - Test plan creation	05/01/2017
QA - Test cases/Env preparation
QA - Nightly Testing	missed	missed
QA - Aurora Testing	05/01/2017
QA - Beta Testing
Release Date

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

Status

Overview

First releases to Nightly:  2016-11-08
Track the dates and build number where feature was merged to Aurora
Track the dates and build number where feature was merged to Release/Beta

Risk analysis

Identify the high-risk assumptions
Identify existing bugs on the feature with high risk
Identify if other areas are affected by the fix

References

• Meta bug 1313406
• Useful info related to this feature can be found at following: TBD

Testcases

Test Areas

Test Areas	Covered	Details
Private Window	TBD
Multi-Process Enabled	TBD
Multi-process Disabled	TBD
Theme (high contrast)	TBD
UI
Mouse-only operation	TBD
Keyboard-only operation	TBD
Display (HiDPI)	TBD
Interraction (scroll, zoom)	TBD
Usable with a screen reader	TBD
Usability and/or discoverability testing	TBD
Help/Support
Help/support interface required	TBD
Support documents planned(written)	TBD
Install/Upgrade
Feature upgrades/downgrades data as expected	TBD
Does sync work across upgrades	TBD
Requires install testing	TBD
Affects first-run or onboarding	TBD
Does this affect partner builds? Partner build testing	TBD
Enterprise
Enterprise administration	TBD
Network proxies/autoconfig	TBD
ESR behavior changes	TBD
Locked preferences	TBD
Data Monitoring
Temporary or permanent telemetry monitoring	TBD
Telemetry correctness testing	TBD
Server integration testing	TBD
Offline and server failure testing	TBD
Load testing	TBD
Add-ons		If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on.
Addon API required?	TBD
Comprehensive API testing	TBD
Permissions	TBD
Testing with existing/popular addons	TBD
Security
3rd-party security review	TBD
Privilege escalation testing	TBD
Fuzzing	TBD
Web Compatibility
Testing against target sites	TBD
Survey of many sites for compatibility	TBD
Interoperability
Common protocol/data format with other software: specification available. Interop testing with other common clients or servers.	TBD
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS	TBD
Interaction of this feature with other browser features	TBD

Test suite

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

Bug Work

Tracking bug – meta bug

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

Results

Nightly testing

Feature came into our radar late so we missed the Nightly testing.

Aurora testing

• Mid-Aurora Sign off
  • Missed
• Pre-Beta Sign off
  • List of OSes that will be covered by testing: Windows 7 x64, Windows 10 x64, Mac OS X 10.11.6, Ubuntu 16.04 x64
    
  • Full Test suite Testrail

Beta testing

• Pre-Release sign-off
  • List of OSes that will be covered by testing: Windows 7 x64, Windows 10 x64, Mac OS X 10.11.6, Ubuntu 14.04 x64
    
  • Full Test suite Testrail

Checklist

Exit Criteria	Status	Notes/Details
Testing Prerequisites (specs, use cases)
Testing Infrastructure setup
Test Plan Creation	In progress
Test Cases Creation	Not started
Full Functional Tests Execution
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
Daily Status Report (email/etherpad statuses/ gdoc with results)
Metrics/Telemetry
QA Signoff - Nightly Release		Missed
QA Aurora - Full Testing	N/A
QA Signoff - Pre-Beta Sign off	[DONE]	Email sent 01/17/2017 (GREEN)
QA Beta - Full Testing	[DONE]
QA Signoff - Pre-Release Sign off	[DONE]	Email sent 02/23/2017 (GREEN)