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/05/2017	1.0	Roxana Leitan	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 Graphics Stability project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:

• Verify that Graphics Stability feature allows animated images to be discarded/re-decoded without glitches

Ownership

Development
Timothy Nikkel (irc: tn)

Engineering QA Team - Nightly Testing:
Rares Bologa (irc: RaresB) - PM for QA team
Brindusa Tot (irc: brindusat) - leading QA efforts
Roxana Leitan (irc: RoxanaLeitan) - QA

Testing summary

Scope of Testing

In Scope

Graphics Stability project enables the feature on Desktop for the animated images (gifs and pngs).

Allow discarding/re-decoding animated images like non-animated images.
Three different types of animated images:
-infinite looping
-finite length that has stopped animating
-finite length that is still animating

Out of Scope

Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.

Requirements for testing

Environments

Full testing will be performed on the following OSes:

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

Channel dependent settings (configs) and environment setups

Test Strategy

Risk Assessment and Coverage

ID	Description / Threat Description	Covered by Test Objective	Magnitude	Probability	Priority	Impact Score
RAC-1	User Experience	TO-1	3-High	2-Possible	2-Medium	12
RAC-2	Graphics	TO-1	3-High	2-Possible	3-High	18
RAC-3	Private window	TO-2	2-Moderate	2-Possible	3-High	12

Values:

• Magnitude: 1- Low , 2-Moderate, 3-High

• Probability: 1-Unlikely, 2-Possible, 3-Almost Certain

• Priority: 1 - Low, 2-Medium, 3-High

Impact Score Breakdown:

• An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
• An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
• An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.

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	RAC	Owners
1	Usability	To ensure a positive user experience	User Experience expectations	Manual	RAC-1	Eng Team
2	Graphics	To verify the correct display of the animations	The animations play without glitches, keep the correct rate and display the correct final frame when stop	Manual	RAC-2	Eng Team
3	Private Browsing	Verify that the feature works while in private browsing	The animations are playing without glitches	Manual	RAC-3	Eng Team

Builds

This section should contain links for builds with the feature - Graphics Stability enabled

• Links for Nightly builds
  • First Landed on Nightly 55.0a1: link on 09.04.2017

• Links for Beta builds
  • First Landed on Beta 55.0a1: link on 13.06.2017

Test Execution Schedule

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

Project phase	Start Date	End Date
Start project	2017.03.31	TBD
Study documentation/specs received from developers	2017.03.31	2017.04.03
QA - Test plan creation	2017.04.05	2017.04.12
QA - Test cases/Env preparation	2017.04.06	2017.04.12
QA - Nightly Testing	2017.04.14	2017.06.02
QA - Beta Testing	2017.07.17	2017.07.19
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	TestRail/ Google docs
Test case execution	TestRail
Bugs management	Bugzilla

Status

Overview

• Landed on Nightly:
  • First Landed on Nightly 55.0a1: link on 09.04.2017
• Nightly sign-off: link on 02.06.2017

• Landed on Beta:
  • First Landed on Beta 55.0a1: link on 13.06.2017

References

• Meta bug Bug 686905 [meta Discard animated images to save memory]

Testcases

Test Areas

Test Areas	Covered	Details
Private Window	Yes
Multi-Process Enabled	Yes
Multi-process Disabled	No
Theme (high contrast)	No
UI
Mouse-only operation	No
Keyboard-only operation	No
Display (HiDPI)	No
Interaction (scroll, zoom)	Yes
Usable with a screen reader	No	e.g. with NVDA
Usability and/or discoverability testing	Yes	Is this feature user friendly
RTL build testing	No
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	No	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	No	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	No
Network proxies/autoconfig	No
ESR behavior changes	No
Locked preferences	No
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	No
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	No
Fuzzing	No
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.	No
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS	No
Interaction of this feature with other browser features	No

Test suite

Full Test suite - Link to test rail - test cases should be added under Firefox Desktop project link
Smoke Test suite - Link with the tests - if available/needed.
Regression Test suite - Link with the tests - if available/needed.

Bug Work

Meta bug: 686905 - bug summary

Sign off

Criteria

Check list

• All test cases should be executed
• 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

Testing will be performed on folowing OSes

• Windows (Windows 7 and Windows 10)
  
• Ubuntu 16.04
  
• Mac OS X 10.12
  

Link for the tests run

• Full Test suite, link to TestRail - Tests Runs and Results link

Merge to Beta Sign-off
Testing will be performed on folowing OSes

• Windows 10
  
• Ubuntu 16.04
  
• Mac OS X 10.10
  

Link for the tests run

• Full Test suite, link to TestRail - Tests Runs and Results link

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	N/A
Performance Testing	N/A
All Defects Logged	[DONE]
Critical/Blockers Fixed and Verified	[DONE]
Metrics/Telemetry	No
QA Nightly Testing - Mid-Nightly Sign-Off	[DONE]	Email sent in 05-16-2017 (YELLOW)
QA Nightly Testing- Pre-Beta Sign-Off	[DONE]	Email sent in
QA Beta Testing - Pre-Release Sign-Off	[IN PROGRESS]	Email to be sent
Live in Release		In release strating with ...