QA/Plugin Compatibility Testing
Revision History
Date | Version | Author | Description |
---|---|---|---|
06/30/2016 | 1.0 | Michelle Funches | Created first draft |
Contents
Overview
Purpose
Detail the purpose of this document.
- The test scope, focus areas and objectives for Plugin Compatibility and Testing
- 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 Plugin Compatibility. 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
What resources are needed, and when (developers, QA, PMs working on the feature)
Testing summary
Scope of Testing
In Scope
Detail what is in scope from a testing perspective for the project team.
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
Specify OSes that need to be covered Specify Devices that need to be covered Specify other configuration/environmental setup needed
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 | Flash Plugin Blocking | The objective the test is trying to demonstrate the effects of blocking specified features related to the plugin | Block specified files such as .swf files on specified sites | Manual | QA Eng Team |
2 | Java Plugin and E10s | The objective of the test is to identify if the Java Plugin with E10s enabled | To determine the root cause of crashes | Manual | QA Eng Team |
3 | |||||
4 |
Flash Games Test List
The following popular flash games are to be tested for Web Compatibility for all Flash related plugin changes
Game | Site |
---|---|
Slotomania | https://apps.facebook.com/169545139744270 |
Caesars Casino | https://apps.facebook.com/275591942465870 |
Bingo Blitz | https://apps.facebook.com/108854979142742 |
House of Fun | https://apps.facebook.com/134672596609680 |
Vegas Downtown Slots | https://apps.facebook.com/997795446916691 |
Poker Heat | https://apps.facebook.com/582934101860851? |
World Series of Poker | https://apps.facebook.com/1375730929320387 |
Farmville | https://www.facebook.com/pages/FarmVille-Facebook/110588968969843 |
Farmville 2 | https://www.facebook.com/FarmVille2/ |
Kongregate | http://www.kongregate.com/games/ |
UI Test Plans
Project | Channel | Test Plan | Test Results | Meta Bug | Date |
---|---|---|---|---|---|
Flash Plugin Blocking | Nightly | Test Plan Link | Test Cases Link | Meta Bug Link | 06-24-2016 |
Java Plugin w/E10s Enabled | Beta | Test Plan Link | Test Case Link | Meta Bug Link | 06-28-2016 |
Asynchronous Plugin Rendering 1.0 | Release 49.0.1 | Test Plan Link | Test Case Link | Meta Bug Link | 10/14/2016 |
Remove - Asynchronous Plugin Rendering 2.0 | Release 49.0.2 | Test Plan Link | Test Case Link | Meta Bug Link | 10/25/2016 |
- Note: