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
08/15/2016	1.0	Adrian Florinescu	Created first draft
09/05/2016	1.1	Roxana Leitan	Updates
09/15/2016	1.2	Adrian Florinescu	TestResults, Bug work and schedule updates
10/20/2016	1.3	Cornel Ionce	Changed ownership, bug work, sign-off results and updates
01/13/2017	1.4	Cornel Ionce	Sign-off results and several other updates

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 Indicator for device permissions project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document what and how we shall test:

• Permissions are listed and correctly managed for devices actively streaming
• The area involving video, audio and stream sharing
• Behavior of the indicator when the resources (audio/video/sharing) are called from a sub-frame

Ownership

Development
Manager: Panagiotis Astithas (irc: past)
Developer contacts: Florian Quèze (irc: florian, flo, flo-retina)

QA:
Florin Mezei - PM for QA team

Andrei Vaida and Cornel Ionce - leading QA efforts

Cornel Ionce, QA

Testing summary

Scope of Testing

In Scope

The testing effort for the Indicator for device permissions will be invested on the following areas:

• functionality: basic and advanced functionality to be verified according to the existing requirements;
• usability: the Indicator for device permissions must be easy to use and straightforward;
• accessibility: the Indicator for device permissions can be used with High Contrast Theme, Keyboard only or Screen Reader;

In the scope of current testing are following permissions:

• Audio
• Video
• Screen or Window Sharing
• Combination between the ones mentioned above

Out of Scope

Following areas are considered out of scope and will not be considered as testing zones to be handled in this test plan:

- Geolocation permission notification
- Pointer lock permission notification

Requirements for testing

Environments

Full testing will be performed on the following OSes:

• Windows, probably Windows 7 and Windows 10
• Mac OS X
• Ubuntu

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	Indicator for device Audio	The objective is trying to demonstrate Microphone Notification is displayed	Microphone Notification is displayed and functions accordingly	Manual	Rel Team
2	Indicator for Camera	The objective is trying to demonstrate Camera Notification is displayed	Camera Notification is displayed and functions accordingly	Manual	Rel Team
3	Indicator for Screen Sharing	The objective is trying to demonstrate Screen Sharing Notification is displayed	Screen Sharing Notification is displayed and functions accordingly	Manual	Rel Team
4	Indicator for Window Sharing	The objective is trying to demonstrate Window Sharing Notification is displayed	Window Sharing Notification is displayed and functions accordingly	Manual	Rel Team
5	Indicator for combinations of above mentioned devices	The objective is trying to demonstrate Notification for multiple devices in use is displayed	Notification for multiple devices in use is displayed and functions accordingly	Manual	Rel Team
6	Accessibility	The objective is trying to demonstrate that feature is usable from accessibility point of view	Testing for accessibility includes: - testing using high Contract themes - Screen Reader validation - Keyboard-only	Manual	Rel Team

Builds

This section should contain links for builds with the feature

• First Nightly build containing this feature
• First Aurora build containing this feature
• Links for Beta builds

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase	Start Date	End Date
Start project	2016.08.10	TBD
Study documentation/specs received from developers	2016.08.10	2016.08.18
QA - Test plan creation	2016.08.15	2016.08.19
QA - Test cases/Env preparation	2016.08.15	2016.08.23
QA - Nightly Testing	2016.08.22	2016.09.16
QA - Aurora Testing	2016.10.12	TBD
QA - Beta Testing	TBD	TBD
Release Date	TBD	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
Test case execution	TestRail
Bugs management	Bugzilla

Status

Overview

The date and build number when feature was released to Nightly: v51.0a1 /20160810030202
Track the date and build number when feature was merged to Aurora: v51.0a2 / 20160919065232
Track the date and build number when 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: 1206233 - Indicator for devices actively streaming or permissions being used
• Mock-ups at : link

Testcases

Test Areas

Test Areas	Covered	Details
Private Window	Yes
Multi-Process Enabled	Yes
Multi-process Disabled	Yes
Theme (high contrast)	Yes
UI
Mouse-only operation	No
Keyboard-only operation	No
Display (HiDPI)	Yes
Interraction (scroll, zoom)	Yes
Usable with a screen reader	Yes	e.g. with NVDA
Usability and/or discoverability testing	Yes	Is this feature user friendly
Help/Support
Help/support interface required	No	Make sure link to support/help page exist and is easy reachable.
Support documents planned(written)	No	Make sure support documents are written and are correct.
Install/Upgrade
Feature upgrades/downgrades data as expected	No
Does sync work across upgrades	No
Requires install testing	No	separate feature/application installation needed (not only Firefox)
Affects first-run or onboarding	N/A	Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned.
Does this affect partner builds? Partner build testing	N/A	yes/no options, add comment with details about who will lead testing
Enterprise		Raise up the topic to developers to see if they are expecting to work different on ESR builds
Enterprise administration	N/A
Network proxies/autoconfig	N/A
ESR behavior changes	N/A
Locked preferences	N/A
Data Monitoring
Temporary or permanent telemetry monitoring	No	List of error conditions to monitor
Telemetry correctness testing	No
Server integration testing	No
Offline and server failure testing	No
Load testing	No
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?	No
Comprehensive API testing	No
Permissions	Yes
Testing with existing/popular addons	No
Security		Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature.
3rd-party security review	No
Privilege escalation testing	Yes
Fuzzing	N/A
Web Compatibility		depends on the feature
Testing against target sites	Yes
Survey of many sites for compatibility	Yes
Interoperability		depends on the feature
Common protocol/data format with other software: specification available. Interop testing with other common clients or servers.	Yes
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS	No
Interaction of this feature with other browser features	Yes

Test suite

Full Test suite - Link with tests in Testrail, link
Regression Test suite - Link with the gdoc - if available/needed.

Bug Work

Tracking bug – meta Bug 1206233 - Indicator for devices actively streaming or permissions being used

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

List of OSes that will be covered by testing

• Link for the tests run
  • Full Test suite, in TestRail at link
  • Regression Test suite, if needed/available

Merge to Aurora Sign-off

• Testing covered the following OSes: Mac OS X 10.11.6, Windows 7 x64, Windows 10 x64 and Ubuntu 14.04 x64
  
  • Test Results can be found in Testrail (requires access) or PDF

Merge to Beta Sign-off

• Testing covered the following OSes: Mac OS X 10.11.5, Windows 7 x64, Windows 10 x64 and Ubuntu 14.04 x64
  
  • Test Results can be found in Testrail (requires access) or PDF

Release Sign-off

• Testing covered the following OSes: Mac OS X 10.11.6, Windows 7 x64, Windows 10 x64 and Ubuntu 12.04 x86
  
  • Test Results can be found in Testrail (requires access) or PDF

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
Performance Testing	N/A
All Defects Logged	[DONE]
Critical/Blockers Fixed and Verified	[DONE]
Metrics/Telemetry
QA Signoff - Nightly Release	[DONE]
QA Signoff - Mid-Aurora	[DONE]
QA Aurora - Full Testing	[DONE]
QA Signoff - Aurora Release		Signed-off on 11/14/2016
QA Beta - Full Testing	[DONE]
QA Signoff - Beta Release		Signed-off on 11.13.2017