QA/Async Drawing Test Plan: Difference between revisions
< QA
Jump to navigation
Jump to search
m (→Ownership) |
m (→Builds) |
||
| Line 109: | Line 109: | ||
== Builds == | == Builds == | ||
Current [https://get.adobe.com/flashplayer/ Adobe Flash Player] is version 24.0.0.194 | Current [https://get.adobe.com/flashplayer/ Adobe Flash Player] is version 24.0.0.194 | ||
These are [http://labs.adobe.com/ Flash Beta Builds] | |||
== Test Execution Schedule == | == Test Execution Schedule == | ||
Revision as of 18:04, 24 January 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 | No significant regression in site correctness or video performance | TBD |
| Flash apps (Popular sites, particularly Facebook and highly popular Flash gaming sites) | No significant regression in site correctness or app/gaming performance | TBD |
| 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
| Criteria Description | Metric | asyncDrawing disabled | asyncDrawing enabled | Criteria Met? | QA Owner |
|---|---|---|---|---|---|
| Manual testing | Test cases passed | # (passed -TBD) out of # (total test cases run -TBD) | # (passed -TBD) out of # (total test cases run -TBD) | TBD (Date status updated) | StephanG ? |
Flash Apps
| Criteria Description | Metric | asyncDrawing disabled | asyncDrawing enabled | Criteria Met? | QA Owner |
|---|---|---|---|---|---|
| Manual testing | Test cases passed | # (passed -TBD) out of # (total test cases run -TBD) | # (passed -TBD) out of # (total test cases run -TBD) | TBD (Date status updated) | StephanG ? |
General Performance
Acceptable regression ranges, if any, need to be determined.
| Criteria Description | Metric | asyncDrawing disabled | asyncDrawing enabled | Criteria Met? | QA Owner |
|---|---|---|---|---|---|
| CPU usage (observed) | Peak/average % CPU | %peak/%average | %peak/%average | TBD (Date status updated) | StephanG ? |
| Memory usage (observed) | Peak/Average % memory | %peak/%average | %peak/%average | TBD (Date status updated) | StephanG ? |
| Telemetry - overall crash rates of Adobe Flash Player | crashes per 1000 use hours | # crashes | # crashes | TBD (Date status updated) | tracy |
Builds
Current Adobe Flash Player is version 24.0.0.194 These are 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 | - |
| QA - Test plan creation | 20170120 | [IN PROGRESS] |
| QA - Test cases/Env preparation | - | - |
| QA - Nightly Testing | - Dec. 2016 | [IN PROGRESS] |
| QA - Aurora Testing | ||
| 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 | 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 TBD
To Be filed:
Overview
- Summary of testing scenarios
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | Yes | |
| Multi-Process Enabled | Yes | |
| Multi-process Disabled | Yes | |
| Theme (high contrast) | No | |
| UI | ||
| Mouse-only operation | Yes | |
| Keyboard-only operation | Yes | |
| Display (HiDPI) | Yes | |
| Interaction (scroll, zoom) | Yes | |
| Usable with a screen reader | Yes | e.g. with NVDA |
| Usability and/or discoverability 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) | Yes | 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 | Yes | Ensure latest Adobe Flash Player |
| Affects first-run or onboarding | No | |
| Does this affect partner builds? Partner build testing | No | |
| 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 | |
| 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 | ||
| 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. | Yes | Adobe Flash Player |
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | No | |
| Interaction of this feature with other browser features | Yes |
Test suite
- Full Test suite - Test Rail - TBD
- We should make sure the full test suite includes bugs that have whiteboard STR from the list below
- Smoke Test suite -* Regression Test suite - TBD
Bug Work
- Bugzilla Meta Bug
- Bugzilla logged bugs -
38 Total; 0 Open (0%); 38 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)
Results
Aurora testing
- TBD on TestRail
Merge to Aurora Sign-off
List of OSes that will be covered by testing
- Link for the tests run - TBD
- Full Test suite - TBD
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | ||
| Testing Infrastructure setup | No | |
| Test Plan Creation | [IN PROGRESS] | |
| Test Cases Creation | [IN PROGRESS] | |
| Full Functional Tests Execution | ||
| Smoke Tests Execution | ||
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | ||
| Critical/Blockers Fixed and Verified | ||
| Daily Status Report (email/etherpad statuses/ gdoc with results) | ||
| Metrics/Telemetry | N/A | |
| QA Signoff - Nightly Release | Email to be sent | |
| QA Aurora - Full Testing | ||
| QA Signoff - Aurora Release | Email to be sent | |
| QA Beta - Full Testing | ||
| QA Signoff - Beta Release | Email to be sent |
Ownership
Product contact:
Engineering contact:
Jim Mathies
QA contact:
Stefan Georgiev
Tracy Walker (IRC: tracy)