QA/Async Drawing Test Plan: Difference between revisions
(Created page with "= Overview = == Purpose == Quality assurance plan to ensure Flash content on Windows are ready for public release. == Quality Criteria == {| class="wikitable" style="width:...") |
|||
(48 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
== Purpose == | == Purpose == | ||
Quality assurance plan to ensure Flash content on Windows | Quality assurance plan to ensure Flash content on Windows with asyncDrawing enabled is ready for public release. | ||
== Quality Criteria == | == Quality Criteria == | ||
Line 9: | Line 9: | ||
! Risk area !! Requirement !! Status | ! Risk area !! Requirement !! Status | ||
|- | |- | ||
| | | Flash videos and apps || No significant regression in site correctness, video performance or app/gaming performance || style="background-color:Tomato;" | 49 Total Bugs, 7 Open (14.29%), 2 Blockers remain | ||
|- | |- | ||
| General performance || Overall performance of asyncDrawing enabled Firefox Adobe Flash Player should not be notably worse than with asyncDrawing not enabled|| style="background-color:#CEF2F2;" | TBD | | General performance || Overall performance of asyncDrawing enabled Firefox Adobe Flash Player should not be notably worse than with asyncDrawing not enabled|| style="background-color:#CEF2F2;" | [https://wiki.mozilla.org/QA/asyncDrawing#General_Performance TBD] | ||
|} | |} | ||
Line 24: | Line 24: | ||
=== Out of Scope === | === Out of Scope === | ||
We will not be testing on obscure web sites | We will not be testing on obscure web sites nor in conjunction with popular add-ons | ||
= Requirements for testing = | = Requirements for testing = | ||
Line 30: | Line 30: | ||
Testing will be performed on following OSes: | Testing will be performed on following OSes: | ||
* Windows 10 ( | * Windows 10 (64bit and 32bit) | ||
* Windows 7 | * Windows 7 | ||
= Quality Assurance Strategy = | = Quality Assurance Strategy = | ||
== Test Items == | == Test Items == | ||
=== Flash Video and Apps === | |||
{| class="wikitable" style="width:95%" | |||
|- | |||
! Criteria Description | |||
! Metric | |||
! asyncDrawing disabled | |||
! asyncDrawing enabled | |||
! Criteria Met? | |||
! QA Owner | |||
|- | |||
| Manual testing | |||
| Test cases passed | |||
| style="background-color:LightGreen;" | 100%[1] | |||
| style="background-color:Coral;" | 49 Total Bugs, 7 Open (14.29%), 2 Blockers remain | |||
| style="" | [https://wiki.mozilla.org/QA/asyncDrawing#Bug_Work Bug List] | |||
| StephanG | |||
|} | |||
[https://docs.google.com/spreadsheets/d/1R841DnaGHROvUZA1MKTz26YbsajSqxycWAtJgNBibtc/edit#gid=0 Bug Triage Spreadsheet] - Includes results from various SoftVision testing rounds and analysis. | |||
[1] All open bugs triaged against both settings. Any bug that was reproducible in both modes removed from bug lists. | |||
=== General Performance === | |||
Acceptable regression ranges, if any, need to be determined through testing. In general, where slow path bitmap based painting is in use (wmode=windowless) we have always had performance issues. As such those sites do not play into our decision making here. We now convert all flash that defaults or is set to use window mode, to direct. In general we haven't seen major performance issues on these sites. | |||
{| class="wikitable" style="width:95%" | |||
|- | |||
! Criteria Description | |||
! Metric | |||
! asyncDrawing disabled | |||
! asyncDrawing enabled | |||
! Criteria Met? | |||
! QA Owner | |||
|- | |||
| CPU usage (observed) | |||
| Average % CPU | |||
| [https://wiki.mozilla.org/QA/asyncDrawing/perf_Testing results] | |||
| [https://wiki.mozilla.org/QA/asyncDrawing/perf_Testing results] | |||
| style="background-color:lightgreen;" | PASS | |||
| style="background-color:lightgreen;" | tracy | |||
|- | |||
| Memory usage (observed) | |||
| Peak memory usage | |||
| [https://wiki.mozilla.org/QA/asyncDrawing/perf_Testing results] | |||
| [https://wiki.mozilla.org/QA/asyncDrawing/perf_Testing results] | |||
| style="background-color:lightgreen;" | PASS | |||
| style="background-color:lightgreen;" | tracy | |||
|} | |||
== Builds == | == Builds == | ||
* Current [https://get.adobe.com/flashplayer/ Adobe Flash Player] | |||
* [http://labs.adobe.com/ Flash Beta Builds] | |||
== Test Execution Schedule == | == Test Execution Schedule == | ||
Line 48: | Line 97: | ||
| Start project | | Start project | ||
|style="text-align:center;" | December 2016 | |style="text-align:center;" | December 2016 | ||
|style="text-align:center;" | | |style="text-align:center;" | June 2017 | ||
|- | |- | ||
| QA - Test plan creation | | QA - Test plan creation | ||
|style="text-align:center;" | 20170120 | |style="text-align:center;" | 20170120 | ||
|style="text-align:center;" | | |style="text-align:center;" | 20170207 | ||
|- | |- | ||
| QA - Test cases/Env preparation | | QA - Test cases/Env preparation | ||
|style="text-align:center;" | | |style="text-align:center;" | 20170120 | ||
|style="text-align:center;" | | |style="text-align:center;" | 20170127 | ||
|- | |- | ||
| QA - Nightly Testing | | QA - Nightly Testing | ||
|style="text-align:center;" | | |style="text-align:center;" | Dec. 2016 | ||
|style="text-align:center;" | | |style="text-align:center;" | Mar. 2017 | ||
|- | |- | ||
| QA - Beta Testing | | QA - Beta Testing | ||
|style="text-align:center;" | | |style="text-align:center;" | April 2017 | ||
|style="text-align:center;" | | |style="text-align:center;" | June 2017 | ||
|- | |- | ||
| Release Date | | Release Date | ||
|style="text-align:center;" | | |style="text-align:center;" | | ||
|style="text-align:center;" | | |style="text-align:center;" | 2017-06-13 | ||
|} | |} | ||
Line 101: | Line 142: | ||
= References = | = References = | ||
Early testing tracked [https://docs.google.com/spreadsheets/d/1R841DnaGHROvUZA1MKTz26YbsajSqxycWAtJgNBibtc/edit#gid=0 here] | |||
= Testcases = | = Testcases = | ||
Available on TestRail or [https://docs.google.com/spreadsheets/d/13BU2fvI7dcWJdQSLDnlCuUissJAMn1eFnuhoOjk_M_A/edit#gid=0 Google Doc] format | |||
Available on TestRail or Google Doc format | |||
== Overview == | == Overview == | ||
* Summary of testing scenarios | * Summary of testing scenarios | ||
== Test | == Test suite == | ||
* Full Test suite - Test Rail - ([https://docs.google.com/spreadsheets/d/13BU2fvI7dcWJdQSLDnlCuUissJAMn1eFnuhoOjk_M_A/edit#gid=0 google doc]) | |||
** We should make sure the full test suite includes bugs that have whiteboard STR from the list below | |||
= Bug Work = | |||
* Bugzilla Meta Bug | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1229961 1229961] <br> | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1340934 1340934] <br> | |||
* Bugzilla logged bugs - | |||
[https://bugzilla.mozilla.org/showdependencytree.cgi?id=1229961&hide_resolved=1 Main List] | |||
<bugzilla> | |||
{ | |||
"f1":"blocked", | |||
"o1":"anywords", | |||
"v1":"1229961,1340934", | |||
"status":["NEW","REOPENED","UNCONFIRMED", "RESOLVED"], | |||
"include_fields":"id,summary,status,resolution,whiteboard" | |||
} | |||
</bugzilla> | |||
= Sign off = | = Sign off = | ||
Line 284: | Line 181: | ||
* All test cases should be executed | * All test cases should be executed | ||
* All blockers, critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA) | * All blockers, critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA) | ||
== Checklist == | == Checklist == | ||
Line 300: | Line 188: | ||
|- | |- | ||
| Testing Prerequisites (specs, use cases) | | Testing Prerequisites (specs, use cases) | ||
| style="text-align:center;" | | | style="text-align:center; background-color:LightGreen;" | Done | ||
| style="text-align:center;" | | | style="text-align:center;" | | ||
|- | |- | ||
| Testing Infrastructure setup | | Testing Infrastructure setup | ||
|style="text-align:center;" | | |style="text-align:center; background-color:LightGreen;" | None || | ||
|- | |- | ||
| Test Plan Creation | | Test Plan Creation | ||
| style="text-align:center;" | | | style="text-align:center; background-color:LightGreen;" | Done || | ||
|- | |- | ||
| Test Cases Creation | | Test Cases Creation | ||
|style="text-align:center;" | | |style="text-align:center; background-color:LightGreen;" | Done || | ||
|- | |- | ||
| Full Functional Tests Execution | | Full Functional Tests Execution | ||
|style="text-align:center;" | | |style="text-align:center; background-color:LightGreen;" | Done || | ||
|- | |- | ||
| | | Automation Coverage | ||
|style="text-align:center; | |style="text-align:center; background-color:LightGreen;" | N/A || | ||
|- | |- | ||
| Performance Testing | | Performance Testing | ||
|style="text-align:center;" | | |style="text-align:center; background-color:Lightyellow;" | {{mprog}} || | ||
|- | |- | ||
| All Defects Logged || || | | All Defects Logged | ||
|style="text-align:center; background-color:LightGreen;" | Done || | |||
|- | |- | ||
| Critical/Blockers Fixed and Verified || || | | Critical/Blockers Fixed and Verified | ||
|style="text-align:center; background-color:Tomato;" | {{mprog}} || | |||
|- | |- | ||
| | | Metrics/Telemetry || | ||
|style="text-align:center;" | Beta | |||
|- | |- | ||
| | | QA Signoff - Nightly Release || | ||
|style="text-align:center;" | | |style="text-align:center;" | Email to be sent | ||
|- | |- | ||
| QA | | QA Beta - Full Testing || | ||
|style="text-align:center;" | Email to be sent | |style="text-align:center;" | Email to be sent | ||
|- | |- | ||
| QA Signoff - Beta Release || | | QA Signoff - Beta Release || | ||
Line 351: | Line 230: | ||
== Ownership == | == Ownership == | ||
Product contact:<br /> | Product contact:<br /> | ||
Engineering contact:<br /> | Engineering contact:<br /> | ||
[mailto:jimm@mozilla.com Jim Mathies]<br /> | |||
QA contact:<br /> | QA contact:<br /> | ||
[mailto:stefan.georgiev@softvision.com Stefan Georgiev]<br /> | |||
[mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br /> | [mailto:twalker@mozilla.com Tracy Walker] (IRC: tracy)<br /> |
Latest revision as of 13:54, 5 June 2017
Overview
Purpose
Quality assurance plan to ensure Flash content on Windows with asyncDrawing enabled is ready for public release.
Quality Criteria
Risk area | Requirement | Status |
---|---|---|
Flash videos and apps | No significant regression in site correctness, video performance or app/gaming performance | 49 Total Bugs, 7 Open (14.29%), 2 Blockers remain |
General performance | Overall performance of asyncDrawing enabled Firefox Adobe Flash Player should not be notably worse than with asyncDrawing not enabled | TBD |
Testing summary
Scope of Testing
In Scope
The scope of our testing is the async drawing functionality and performance of the most popular sites and games with latest Adobe Flash Player.
- Integration: Verify the integration with the current browser functionalities and UI;
- Functionality: Basic and advanced functionality to be verified according to the existing requirements;
- Performance: Reference, where applicable, observed and collected performance data.
Out of Scope
We will not be testing on obscure web sites nor in conjunction with popular add-ons
Requirements for testing
Environments
Testing will be performed on following OSes:
- Windows 10 (64bit and 32bit)
- Windows 7
Quality Assurance Strategy
Test Items
Flash Video and Apps
Criteria Description | Metric | asyncDrawing disabled | asyncDrawing enabled | Criteria Met? | QA Owner |
---|---|---|---|---|---|
Manual testing | Test cases passed | 100%[1] | 49 Total Bugs, 7 Open (14.29%), 2 Blockers remain | Bug List | StephanG |
Bug Triage Spreadsheet - Includes results from various SoftVision testing rounds and analysis.
[1] All open bugs triaged against both settings. Any bug that was reproducible in both modes removed from bug lists.
General Performance
Acceptable regression ranges, if any, need to be determined through testing. In general, where slow path bitmap based painting is in use (wmode=windowless) we have always had performance issues. As such those sites do not play into our decision making here. We now convert all flash that defaults or is set to use window mode, to direct. In general we haven't seen major performance issues on these sites.
Criteria Description | Metric | asyncDrawing disabled | asyncDrawing enabled | Criteria Met? | QA Owner |
---|---|---|---|---|---|
CPU usage (observed) | Average % CPU | results | results | PASS | tracy |
Memory usage (observed) | Peak memory usage | results | results | PASS | tracy |
Builds
- Current Adobe Flash Player
- Flash 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 | December 2016 | June 2017 |
QA - Test plan creation | 20170120 | 20170207 |
QA - Test cases/Env preparation | 20170120 | 20170127 |
QA - Nightly Testing | Dec. 2016 | Mar. 2017 |
QA - Beta Testing | April 2017 | June 2017 |
Release Date | 2017-06-13 |
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
- Track the dates and build number where feature was released to Nightly
- 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
References
Early testing tracked here
Testcases
Available on TestRail or Google Doc format
Overview
- Summary of testing scenarios
Test suite
- Full Test suite - Test Rail - (google doc)
- We should make sure the full test suite includes bugs that have whiteboard STR from the list below
Bug Work
- Bugzilla logged bugs -
62 Total; 0 Open (0%); 62 Resolved (100%); 0 Verified (0%);
Sign off
Criteria
Check list
- All Criteria under each section of Quality Assurance Strategy should be green.
- All test cases should be executed
- All blockers, critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)
Checklist
Exit Criteria | Status | Notes/Details |
---|---|---|
Testing Prerequisites (specs, use cases) | Done | |
Testing Infrastructure setup | None | |
Test Plan Creation | Done | |
Test Cases Creation | Done | |
Full Functional Tests Execution | Done | |
Automation Coverage | N/A | |
Performance Testing | [IN PROGRESS] | |
All Defects Logged | Done | |
Critical/Blockers Fixed and Verified | [IN PROGRESS] | |
Metrics/Telemetry | Beta | |
QA Signoff - Nightly Release | Email to be sent | |
QA Beta - Full Testing | Email to be sent | |
QA Signoff - Beta Release | Email to be sent |
Ownership
Product contact:
Engineering contact:
Jim Mathies
QA contact:
Stefan Georgiev
Tracy Walker (IRC: tracy)