QA/Asynchronous Plugin Rendering

Revision History

This section describes the modifications that have been made to this wiki page.

Date	Version	Author	Description
10/11/2016	1.0	Michelle Funches	Created first draft

Overview

Purpose

The purpose of this document is to support the purpose and testing for the Asynchronous Plugin Rendering System AddOn.

Scope

This wiki details the testing that will be performed by SV Las Vegas for the Asynchronous Plugin Rendering System Addon. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:

• What will be tested
• How testing will be performed

Ownership

Mozilla Development
Brad Lassey
Kirk Steuber

QA Engineering
Michelle Funches

Testing summary

Scope of Testing

In Scope

What will be tested: Asynchronus Plugin Rendering System AddOn, Adobe Beta 23. Testing for issues with plugin rendering/painting or event input issues.

Out of Scope

Testing will not include iOS or Android devices.

Requirements for testing

Environments

Testing will be performed on the current Release Firefox 49.0.1 with the AddOn installed. Testing will focus on Windows OS where the Async Drawing API is effected. Platforms include:
Windows 7
Windows 8.1
Windows 10
Testing will include Firefox 32-bit and Firefox 64-bit.

Test Strategy

Test Objectives

Ref	Function	Test Objective	Evaluation Criteria	Test Type	Owners
1	Asynchronous Plugin Rendering 1.0	The objective the test is trying to demonstrate the addon functions as desired	The criteria that will be evaluated to demonstrate the test is successful	Manual	SV-Vegas Eng Team

Test Execution Schedule

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

Project phase	Start Date	End Date
Start project	10/10/2016
Study documentation/specs received from developers	10/10/2016
QA - Test plan creation	10/11/2016
QA - Test cases/Env preparation	10/10/2016
Release firefox 49.0.1 with the AddOn installed	10/10/2016

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 Doc
Test case execution	Google Doc
Bugs management	Bugzilla

Risk analysis

Bug 1307108
Bug 1217665

Testcases

Overview

Testing is to focus on Multiprocess enabled. The System AddOn will change the pref. Testing will ensure the AddOn does what it is designed to do and basic Web Compatibility does not produce issues with the plugin or rendering.

Test Areas

Test Areas	Covered	Details
Private Window	Done
Multi-Process Enabled	Done
Multi-process Disabled	N/A
UI
Interaction (scroll, zoom)	Done
Usability and/or discover-ability testing	Done
Web Compatibility
Testing against target sites	Done
Survey of many sites for compatibility	Done

Test suite

Full Test suite -  link
Smoke Test suite -  link

Bug Work

Tracking bug

Bug fix verification

Bug No	Summary	Status	Firefox Verion
1309037	Async Rendering Plugin 1.0 AddOn-Firefox 49.0.1-Adobe Flas 23.0 - Unresponsive Script & Slowness	NEW	Release 49.0.1

Logged bugs

Bug 1309037
Bug

Sign off

Criteria

Check list

• All test cases should be executed
• All Blocks and Critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)

|}