QA/Tab visual sound indicator

From MozillaWiki
< QA
Jump to: navigation, search

Tab visual sound indicator

Overview

Purpose

The purpose of this wiki is to serve as a general test plan for verifying that the tab sound indicator works as expected.

Scope

The testing will be focus on

  • verify that the tab sound indicator works correct
  • verify several edge cases related to this tab indicator

Testing will be performed manually, by QA Release team.

Ownership

Developer contact: Ehsan Akhgari mail

QA Lead: Camelia Badau, :cbadau on IRC

Summary

When multiple tabs are getting opened in short notice, it is difficult to determine in which tab is causing sound or music to play automatically.

  • Example, if you have some tabs open, it is not clear quickly which tab is causing the sound.

The solution is to provide visual indication in tab title that the website is causing sound, so it can be quickly muted or attended to. An icon is displayed in tabs that play sound and additionally allows users to mute such tabs. Because of the audio indicator on each tab, the user can see which tab is playing audio at any moment. Let's explore how it works.
Once you open some tab which plays audio (or a video with sound), Firefox will add a speaker icon to the right side of the tab:

Defaultt.png

The user can click it to mute the sound for the tab:

Mutestate.png

The sound indicator appears for the following pages with audio/video : HTML5, WEBM, OGV, MP4, MP3, OGG, OPUS audio, Web Audio API and for Adobe Flash Player plugin.

Generally, testing involves checking that the indicator tab appears on every page with video / audio content and can be muted/unmuted and not appears on the page without sound.

Requirements for testing

Environments

Testing will be performed on following OSes (both x86 & x64 infrastructures):

  • Mac OS X 10.9.5
  • Windows 7
  • Windows 10
  • Ubuntu 13.10

Testing on specific devices is not needed.

Enabling the feature

  • Enabled by default in Nightly:
    • Build from 2015-08-10 bug

Test Types

Type of Testing Required (Yes/No) Owners Details/Comments
Manual Yes Moz QA Rel team
Automation No
Performance No
Security No

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 Google docs
Test case execution Google docs
Bugs management Bugzilla

Status

Overview

[LANDED] Nightly 43: landed

[LANDED] Aurora 42: landed

Risk analysis

- No Risks found at the moment

Test cases

Bug work

Tracking bug
RESOLVED FIXED (may need verification)

Bug 1195051 - Creating an AudioContext shows the tab sound indicator even without anything playing
Bug 1193749 - Use standard modifier keys for the Mute Tab keyboard shortcut
Bug 1192568 - Update the tab audio icons
Bug 1191959 - Mute tab audio sometimes renders pinned tabs unclickable
Bug 1186267 - Add a keyboard shortcut for toggling the tab mute state
Bug 1183700 - Don't prevent playback of media elements in a muted tab on desktop
Bug 1180523 - Enable muting tabs and controlling their volumes in a way that persists across navigations
Bug 1177399 - Enable AudioChannelService in desktop by default
Bug 1167690 - Support Flash for the audio channel notifications indicating when audio playback starts/stops

VERIFIED FIXED

Bug 1200208 - Tab audio indicator doesn't show up on the huffingtonpost Parkersburg article
Bug 1195150 - Persist the tab muted state in the session store
Bug 1193830 - Clicking on the icon to mute then unmute (or unmute then mute) without moving the mouse off the icon switches tabs
Bug 1193085 - [e10s] Tab audio indicator is still shown after navigating from audio-playing page loaded in a remote page to one in a non-remote page
Bug 1192063 - Z-Order bug when mousing over tab-audio icon
Bug 1191491 - tab audio-indicator disappears when dragging tab to a new window
Bug 1191081 - mute the tab after restoring it from a crash if it was previously muted
Bug 1191038 - Remove the sound playing icon when the browser crashes
Bug 1190106 - tab-sound-icon indicate wrong state after the tab was moved to another browser by drag & drop
Bug 1190081 - We should keep the muted icon on the tab if the media element pauses its playback
Bug 1190040 - tab audio-indicator incorrectly shown for media without sound
Bug 1190023 - Tab sound icon shows on pages with <video muted>
Bug 1189772 - Tab muting doesn't work with some Flash, such as Pandora and Twitch
Bug 1188718 - Don't change the currently selected tab when clicking on the audio mute button
Bug 1188114 - Update tab audio icon tooltip to reflect what clicking does
Bug 1189759 - Add tab sound icon to subject tab in tabs list drop-down
Bug 1193749 - Use standard modifier keys for the Mute Tab keyboard shortcut
Bug 1200236 - Tab audio indicator displays incorrect tooltip after move to new window
Bug 1199929 - Tooltip for muting / unmuting a tab should only contain the keyboard shortcut if it's the selected tab
Bug 1197569 - Can't unmute tab audio indicator after change to a complete theme which is not support tab-audio
Bug 1185303 - After muting a tab, and switching to a new tab, the media element stops

INVALID

Bug 1197062 - Audio indicator position strange in dev edition theme on pinned tab
Bug 1196657 - Ctrl+M should not display the tab audio indicator (on mute state) on a non-audio page
Bug 1196192 - Mute tab audio indicator is displayed even if navigate to any non-audio pages
Bug 1196192 - Cannot Mute video from imdb.com
Bug 1192161 - Tab audio indicator not shown for Flash animations on zombo.com and homestarrunner.com
Bug 1198771 - Active sound indicator icon is not displayed on CNN site (maybe somewhere else, too)

NEW

Bug 1193191 - Provide default status for sound activation in website permissions (about:permissions)
[REOPENED] Bug 1191437 - The mute icon flashes the first time that you click on it on a window
Bug 1213154 - tab-sound-icon does not display after back/forward navigation

UNCONFIRMED

Bug 1196056 - Investigate how the sound indicator affects clicking on a pinned tab with sound

Sign off

Criteria

  • All the test cases were executed.
  • No blocker, critical, major bugs.

Results