QA/Implement support for WebM Alpha

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/06/2017 1.0 Mihai Boldan Created first draft
03/07/2017 1.1 Mihai Boldan pre-Beta Sign off updates



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


This wiki details the testing that will be performed by the project team for the Implement support for WebM Alpha project. Its purpose is to document:

  • What will be tested
  • How testing will be performed


EPM: Anthony Jones , :kentuckyfriedtakahe, :k17e on IRC

Developer contacts: Matthew Gregan , :kinetik on IRC and Karolien Koorts , :karolien on IRC

QA Lead: Mihai Boldan, :mboldan on IRC

Testing summary

Scope of Testing

In Scope

The testing efforts will be invested on the following areas:

  • functionality: TBD
  • usability: TBD
  • performance: make sure that browser performance is not affected
  • accessibility: High Contrast themes, Keyboard operation

Out of Scope


Requirements for testing


Full Testing will be performed on:

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

Exploratory/Smoke testing will be performed on

  • Windows 8
  • Ubuntu 14.04
  • Mac OS X 10.11

Specify other configuration/environmental setup needed:

  • TBD

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


This section should contain links for builds with the feature:

  • Links for Nightly builds
  • Links for Aurora builds
  • 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
Study documentation/specs received from developers
QA - Test plan creation 02/06/2017
QA - Test cases/Env preparation 02/07/2017
QA - Nightly Testing MISSED
QA - Aurora Testing 02/07/2017 02/07/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



  • First releases to Nightly: TBD Nightly build]
  • 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


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


Testcases can be found in Google doc , or Test rail

Test Areas

Test Areas Covered Details
Private Window Yes
Multi-Process Enabled Yes
Multi-process Disabled No
Theme (high contrast) Yes
Mouse-only operation Yes
Keyboard-only operation Yes
Display (HiDPI) Yes
Interraction (scroll, zoom) Yes
Usable with a screen reader NO
Usability and/or discoverability testing YES
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.
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
Enterprise administration No
Network proxies/autoconfig No
ESR behavior changes No
Locked preferences No
Data Monitoring
Temporary or permanent telemetry monitoring Yes
Telemetry correctness testing Yes
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
3rd-party security review No
Privilege escalation testing No
Fuzzing No
Web Compatibility
Testing against target sites Yes
Survey of many sites for compatibility Yes
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 - Gdoc, follow the format from Full Test Cases and for Test Rail, follow the format Full Test Cases
  • 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

Bug fix verification

Here's the list of the verified bugs for the Implement support for WebM Alpha [TBD link]

Logged bugs

Here is the list of logged bugs [TBD link]

Sign off


Check list

  • All test cases should be executed
  • Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
  • All blockers, critical must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)


Nightly testing

List of OSes that will be covered by testing

  • Link for the tests run
    • Daily Smoke, use template from [TBD Test rail]
    • Full Test suite, use template from [TBD Test rail]
    • 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


Exit Criteria Status Notes/Details
Testing Prerequisites (specs, use cases)
Testing Infrastructure setup
Test Plan Creation In progress
Test Cases Creation DONE 02/07/2017
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)
QA Signoff - Nightly Release None MISSED
QA Aurora - Full Testing DONE 2/15/2017
QA Signoff - Aurora Release GREEN Email sent in 2/16/2017
QA Beta - Full Testing
QA Signoff - Beta Release Email to be sent