QA/Block Playback
Revision History
This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded). The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.
| Date | Version | Author | Description |
|---|---|---|---|
| 10/17/2016 | 1.0 | Adrian Florinescu | Initial Draft |
Overview
Purpose
Detail the purpose of this document. For example:
- The test scope, focus areas and objectives
- 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 Block Playback project. 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
• Program Management:
• Engineering Program Manager:
• Eng.:
• UX:
• QA Engineering Team - Nightly Testing
- Rares Bologa (irc: RaresB) - PM for QA team
- Brindusa Tot (irc: brindusat) - leading QA efforts
- Simona Badau (irc: simonab) - QA
• QA Release Team - Aurora/Beta/Release Testing
- Andrei Vaida (irc: avaida) - TL for QA team
- Emil Ghitta (irc: emilghitta) - QA
- Bogdan Maris (irc: bogdan_maris) - QA peer
Testing summary
Scope of Testing
In Scope
The Block Playback feature is designed to block media with enabled autoplay if the tabs are opened in the background. Videos which autoplay in the background will now have their load deferred until the tab is visible for the first time -- this avoids autoplay during session restore and premature playback. Resources will still be preloaded but Firefox will delay the start of playback until the tab that contin a video with an enabled autoplay is visited. Once a tab / RenderFrame has ever played media before, it's allowed to continue to autoplay/autoload indefinitely; this is to support playlist type applications. The main advantages of the Block Playback feature is that it prevents obviously user annoyance but also conserves power as Firefox will only consume power once the tab is foregrounded.
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
Full testing will be performed on the following OSes:
- Windows 7 x64, Windows 10 x64.
- macOS 10.12
- Ubuntu 16.04 x86
Other configuration/environmental setup needed:
- In Firefox configuration settings media.block-autoplay-until-in-foreground preference needs to be set to true.
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 | Test Type | RAC | Owners |
|---|---|---|---|---|---|
| TO-1 | Video playback is not started until tab is visible for the first time | Prevent Video playback until the tab is visible | Manual | RAC-1, RAC-2, RAC-4 | Eng Team |
| TO-2 | Video resources are still pre-loaded even though the tab wasn't visited yet | In the cases in which video playback is blocked, the resources are still being pre-loaded | Manual | - | Eng Team |
| TO-3 | Notification sounds are blocked also for tabs not yet first visited | The sounds from websites such Facebook, Gmail, Hangout, web-Skype are blocked until the tab is visited for first time | Manual | - | Eng Team |
| TO-4 | Performance is acceptable in case of multiple tabs and doesn't crash the browser or media container | TBD what are the expectation in terms of "acceptable" | Manual | RAC-3 | Eng Team |
Impact Score Breakdown:
- An impact value of 1 or 2 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
- An impact value of 4, 8 or 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
- An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.
RAC: Refers to the "Risk Assessment and Coverage" item that is covering.
Builds
This section should contain links for builds with the feature:
- Links for Nightly builds - available since November 11th 2016 link
- Links for Aurora builds - available since March 3rd 2017 link
- Links for 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 | 10.03.2016 | |
| Study documentation/specs received from developers | 10.11.2016 | 10.17.2016 |
| QA - Test plan creation | 10.18.2016 | 10.20.2016 |
| QA - Test cases/Env preparation | 10.20.2016 | 01.11.2017 |
| QA - Nightly Testing | 11.22.2016 | 17.02.2017 |
| QA - Aurora Testing | 03.17.2017 | 03.21.2017 |
| 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/ Google docs |
| Test case execution | TestRail |
| Bugs management | Bugzilla |
Status
(01.23.2017) - For the time being Block Playback feature will be kept enabled only on Nightly - Bug 1331317. (03.07.2017) - Block Playback feature has reached Developer Edition 54.0a2.
Overview
Track the dates and build number where feature was released to Nightly - 52.0a1 (2016-11-12) Track the dates and build number where feature was merged to Aurora - 54.0a2 (2017-03-07) Track the dates and build number where feature was merged to Release/Beta
Risk Assessment and Coverage
| ID | Description / Threat Description | Covered by Test Objective | Magnitude | Probability | Priority | Impact Score |
|---|---|---|---|---|---|---|
| RAC-1 | Mouse and keyboard actions may not be recognized | TO-1 | 2-Moderate | 1-Unlikely | 3-High | 6 |
| RAC-2 | Restoring after a crash or after a session may impact the performance of this feature | TO-1 | 1- Low | 2-Possible | 3-High | 6 |
| RAC-3 | Possible performance issues with multiple tabs | TO-4 | 2-Moderate | 2-Possible | 3-High | 12 |
| RAC-4 | After visiting for the first time a tab containing a video, the video starts with a delay | TO-1 | 3-High | 3-Almost Certain | 3-High | 27 |
Values:
- Magnitude: 1- Low , 2-Moderate, 3-High
- Probability: 1-Unlikely, 2-Possible, 3-Almost Certain
- Priority: 1 - Low, 2-Medium, 3-High
Impact Score Breakdown:
- An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
- An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
- An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.
References
- List and links for specs
https://wiki.mozilla.org/Firefox/Block_Playback https://mozilla.invisionapp.com/share/6T8UPZR8K#/screens
- bug 1308154 - [Meta] (block-autoplay-media) [meta] Block autoplay media until the tab is visible at first time
Testcases
Full testsuites can be found on TestRail at link or in the PDF doc
Overview
Summary of testing scenarios
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | Yes | |
| Multi-Process Enabled | Yes | |
| Multi-process Disabled | No | |
| Theme (high contrast) | Yes | |
| UI | ||
| Mouse-only operation | Yes | |
| Keyboard-only operation | Yes | |
| Display (HiDPI) | Yes | |
| Interraction (scroll, zoom) | No | |
| Usable with a screen reader | No | e.g. with NVDA |
| Usability and/or discoverability testing | Yes | Is this feature user friendly |
| RTL build testing | Yes | |
| Help/Support | ||
| Help/support interface required | No | Make sure link to support/help page exist and is easy reachable. |
| Support documents planned(written) | No | 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 | No | separate feature/application installation needed (not only Firefox) |
| Affects first-run or onboarding | TBD | Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned. |
| Does this affect partner builds? Partner build testing | No | yes/no options, add comment with details about who will lead testing |
| 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 | Yes | TAB_AUDIO_INDICATOR_USED, TAB_MEDIA_BLOCKING_TIME_MS |
| 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 | Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature. | |
| 3rd-party security review | TBD | |
| Privilege escalation testing | No | |
| Fuzzing | No | |
| Web Compatibility | depends on the feature | |
| Testing against target sites | NO | |
| Survey of many sites for compatibility | NO | |
| Interoperability | depends on the feature | |
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | No | |
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | No | |
| Interaction of this feature with other browser features | No |
Test suite
Full Test suite - Link with the gdoc, follow the format from link Smoke Test suite - Link with the gdoc, follow the format from link Regression Test suite - Link with the gdoc - if available/needed.
Bug Work
Meta bug: 1308154 - (block-autoplay-media) [meta Block autoplay media until the tab is visible at first time]
Logged bugs ( blocking 1308154 )
46 Total; 0 Open (0%); 30 Resolved (65.22%); 16 Verified (34.78%);
Bug fix verification
| ID | Priority | Component | Assigned to | Summary | Status | Resolution | Target milestone |
|---|---|---|---|---|---|---|---|
| 1262053 | P3 | Audio/Video: Playback | Alastor Wu [:alwu] | Block playback of media until document is visible | VERIFIED | FIXED | mozilla51 |
| 1302350 | P3 | Audio/Video: Playback | Alastor Wu [:alwu] | Refactor the block-media-element feature. | RESOLVED | FIXED | mozilla52 |
| 1308153 | P3 | Audio/Video: Playback | Alastor Wu [:alwu] | Implement the new UX visual mechanism for blocking autoplay media | RESOLVED | FIXED | mozilla52 |
| 1308399 | P3 | Audio/Video: Playback | Mark Liang(:mark_liang) | [UX] UX Spec for Delay Autoplay | RESOLVED | FIXED | --- |
| 1314220 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Add the Telemetry for blocking autoplay media | VERIFIED | FIXED | mozilla53 |
| 1319529 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | The unblocking icon didn't be hided when resuming Flash | RESOLVED | FIXED | mozilla53 |
| 1319771 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | If the pinned tab is the first tab in the tab list, the media won't be blocked after browser restarts | VERIFIED | FIXED | mozilla54 |
| 1320005 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Don't show 'play tab' icon for video without audio track | VERIFIED | FIXED | mozilla53 |
| 1322505 | P1 | Audio/Video: Playback | Alastor Wu [:alwu] | Don't resume the video after calling video.pause() | VERIFIED | FIXED | mozilla53 |
| 1328058 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Tab displays "play" button or sound indicator when the only media element is playing and has no sound | VERIFIED | FIXED | mozilla54 |
| 1329170 | P3 | Audio/Video: Playback | Alastor Wu [:alwu] | Play Tab indicator looks pixelated in pinned tabs | VERIFIED | FIXED | mozilla54 |
| 1329179 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Play Tab indicator is displayed on a foreground tab | VERIFIED | FIXED | mozilla54 |
| 1330232 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Blocked media was resumed with sound when user click "mute tab" in the pop-up menu | RESOLVED | FIXED | mozilla53 |
| 1330681 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Play tab indicator has no hover state in pinned tabs | VERIFIED | FIXED | mozilla54 |
| 1331317 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Only enable pref "media.block-autoplay-until-in-foreground" on Nightly | VERIFIED | FIXED | mozilla53 |
| 1336309 | -- | Tabbed Browser | Alastor Wu [:alwu] | Modify the access key for "play tab" option | VERIFIED | FIXED | Firefox 54 |
| 1337232 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Enable pref "media.block-autoplay-until-in-foreground" by default | VERIFIED | FIXED | mozilla54 |
| 1338137 | P1 | Audio/Video: Playback | Alastor Wu [:alwu] | If the first tab is pinned and muted - media is not blocked after browser restart | VERIFIED | FIXED | mozilla54 |
| 1343465 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | The tab should show the "play tab" icon even the tab was muted. | RESOLVED | FIXED | mozilla54 |
| 1347758 | P1 | Audio/Video: Playback | Alastor Wu [:alwu] | HTML5 video/audio doesn't play if node was removed in background tab | RESOLVED | FIXED | mozilla55 |
| 1347791 | -- | Tabbed Browser | Alastor Wu [:alwu] | The pinned tab shows play tab icon every time when restarts browser | VERIFIED | FIXED | Firefox 56 |
| 1352014 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Add the flag "RELEASE_OR_BETA" for the pref "media.block-autoplay-until-in-foreground" | RESOLVED | FIXED | mozilla55 |
| 1387917 | -- | Audio/Video: Playback | Alastor Wu [:alwu] | Turn on the pref "media.block-autoplay-until-in-foreground" by default | RESOLVED | FIXED | mozilla57 |
| 1394455 | P1 | Audio/Video: Playback | Mike Conley (:mconley) (:⚙️) | [e10s] Media is unblocked while hovering an unfocused tab | VERIFIED | FIXED | mozilla57 |
| 1572798 | P2 | DOM: Core & HTML | Emilio Cobos Álvarez (:emilio) | Video element created using document.open() doesn't work | RESOLVED | FIXED | 86 Branch |
| 1684876 | -- | Tabbed Browser | kz04px | "Mute Tab" sometimes starts playing the tab's video, with sound | RESOLVED | FIXED | 95 Branch |
| 1733902 | P3 | Audio/Video: Playback | Alastor Wu [:alwu] | Autoplay fails if the player is switched in a background tab | VERIFIED | FIXED | 96 Branch |
27 Total; 0 Open (0%); 11 Resolved (40.74%); 16 Verified (59.26%);
Sign off
Criteria
Check list
- All test cases should be executed
- Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
- All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)
Results
Nightly testing
List of OSes that will be covered by testing
- Link for the tests run -link
Merge to Aurora Sign-off
List of OSes that will be covered by testing
- Link for the tests run -link
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | [DONE] | |
| Testing Infrastructure setup | [DONE] | |
| Test Plan Creation | [DONE] | |
| Test Cases Creation | [DONE] | |
| Full Functional Tests Execution | [DONE] | |
| Automation Coverage | IN PROGRESS |
http://searchfox.org/mozilla-central/source/toolkit/content/tests/browser/browser_block_autoplay_media.js |
| Performance Testing | N/A | |
| All Defects Logged | [DONE] | |
| Critical/Blockers Fixed and Verified | [DONE] | |
| Metrics/Telemetry | [DONE] | |
| QA Signoff - Nightly Release | [DONE] | [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 |