QA/Platform/Graphics/Features/Unaccelerated Compositor Process
From MozillaWiki
Contents
Overview
Purpose
The purpose of this document is to describe the Unaccelerated Compositor Process feature from a testing perspective, including the following details:
- Scope, focus areas and objectives of testing
- Owners and points of contact for areas of responsibility
- Strategy and types of testing
- 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
Ownership
Responsibility | Role | Person |
---|---|---|
Accountable | Engineering Manager | Milan Sreckovic (:milan) |
Responsible | Tech Lead | David Anderson (:dvander) |
Responsible | QA Lead | Anthony Hughes (:ashughes) |
Supporting | Testing | Alexandru Simonca (Softvision) |
Scope
The following is in scope for testing:
- Windows 7 Platform Update and later
- Systems with hardware that is blacklisted or otherwise unable to activate hardware acceleration
- Systems with hardware that is capable of hardware acceleration but have hardware acceleration disabled
The following is out of scope for testing:
- Linux
- Mac OS
- Windows 7 prior to Platform Update
Schedule
April 14, 2017 | Feature lands in Nightly 55 |
June 12, 2017 | Feature moves to Nightly 56 (does not ride to Beta) |
August 8, 2017 | Feature ships to Beta 56 |
September 26, 2017 | Feature ships to Firefox 56 |
Test Coverage
- Operating Systems:
- Windows 7 Platform Update
- Windows 8
- Windows 10
- 32-bit and 64-bit versions
- Hardware:
- AMD graphics cards with latest stable and beta driver versions
- Intel graphics cards with latest stable and beta driver versions
- NVIDIA graphics cards with latest stable and beta driver versions
- Software:
- 32-bit versions of Firefox with and without themes enabled
- 64-bit versions of Firefox with and without themes enabled
- Displays:
- Single and multiple display configurations
- Lo-DPI and Hi-DPI configurations
- Default, first-party, and third-party custom themes (OS-level and Firefox)
- Use cases:
- Make sure a GPU Process is activated when hardware acceleration is enabled
- Make sure a GPU Process is activated when hardware acceleration is disabled
- Make sure a GPU Process is *not* activated when layers.gpu-process.software is disabled
- Conduct top-site A/B testing with and without a GPU Process (incl. video, webgl, canvas, svg, PDFs, and other "rich content" websites)
- Look for:
- Stability problems which only occur when the GPU Process is active
- Performance problems which only occur when the GPU Process is active
- Correctness problems which only occur when the GPU Process is active
Release Criteria
- Nightly > Beta sign-off
- [DROPPED] Telemetry A/B experiment finds no major divergences in stability (Owner: Anthony Hughes) - bug 1367246 blocked by bug 1367823
- [DONE] Manual testing by Softvision finds no major regressions (Owner: Softvision)
- [DONE] Bug triage by Softvision finds no major regressions (Owner: Softvision)
- [DONE] Top crash triage finds no major stability regressions (Owner: Anthony Hughes)
- [DONE] Sign-off email to Drivers (Owner: Softvision)
- Release notes verified and signed off (Owner: Anthony Hughes)
- Beta > Release sign-off
- Telemetry A/B experiment finds no major divergences in stability (Owner: Anthony Hughes)
- Manual testing by Betabreakers finds no major regressions (Owner: Anthony Hughes)
- Manual testing by Softvision finds no major regressions (Owner: Softvision)
- Bug triage by Softvision finds no major regressions (Owner: Softvision)
- Top crash triage finds no major stability regressions (Owner: Anthony Hughes)
- Community testing during at least one testday reveals no major regressions (Owner: Softvision)
- User feedback channels reveal no major regressions (Owner: Softvision)
- Release notes verified and signed off (Owner: Anthony Hughes)
- Sign-off email to Drivers (Owner: Softvision)
Bugs
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);