QA/Video Play Visual Refresh
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 |
|---|---|---|---|
| 12/08/2016 | 1.0 | Brindusa Tot | Created first draft |
Contents
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 Video Play Visual Refresh 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
Development Team:
Vance Chen - irc: vchen - Project Manager
Ray Lin - Developer
Jared Wein - irc: jaws - Developer (Reviewer)
Daniel Holbert - irc:dholbert - Developer (Reviewer)
Peko Chen - irc: peko - UX lead
Engineering Team - Nightly Testing:
Rares Bologa (irc: RaresB) - PM for QA team
Brindusa Tot (irc: brindusat) - leading QA efforts
Hani Yacoub (irc: hani) - QA
Release QA Team - Aurora & Beta Testing:
Ionce Cornel (irc: cornel_ionce)
Iulia Cristescu (irc: IuliaC)
Bogdan Maris (irc: bogdan_maris)
Testing summary
Scope of Testing
In Scope
This feature is a redesign of the video Player in Firefox, so testing should include different types of videos, like avi, mp4, mp3, ogg, WebM.
Testing will be done on 4 OSes:
- Windows 10, Windows 7
- Mac OS X 10.12
- Ubuntu 16.04
Out Of Scope
We are not testing video play on different web sites that have plugins incorporated, like Youtube, Amazon, Netflix.
Requirements for testing
Environments
Full testing will be performed on the following OSes:
- Windows 7 and Windows 10
- Mac OS X 10.12
- Ubuntu 16.04
Channel dependent settings (configs) and environment setups
Nightly
text
Aurora
text
Beta
text
Post Beta / Release
text
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 | Risk Assessment and Coverage(RAC) | Owners |
|---|---|---|---|---|---|
| TO-1 | Video play controllers display | The new visual design is displayed and videos are played correctly | Manual | RAC-1, RAC-4 | Eng Team |
| TO-2 | Video play controllers functionality | The basic functions(play/stop/pause, drag the play progress bar, mute, volume control, full screen) all work properly | Manual | RAC-1 | Eng Team |
| TO-3 | Different video types | Validate that new video player design works correctly on different videos types | Manual | RAC-2 | Eng Team |
| TO-4 | Performance is acceptable in case of multiple tabs and doesn't crash the browser | The objective the test is trying to demonstrate that new videos player design works correctly when videos are opened on multiple tabs or windows | Manual | RAC-3 | Eng Team |
| TO-5 | Accessibility | Testing for accessibility includes:
- testing using high Contract themes |
Manual | RAC-1 | Eng Team |
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 | Some Video types are not recognized and played | TO-3 | 3- High | 2-Possible | 3-High | 18 |
| 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.
Builds
This section should contain links for builds with the feature -
- Links for Nightly builds - available since November 20 2016 - link
- Links for Aurora builds - http://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-aurora/ (53.0a2)
- 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 | 2016.11.28 | |
| Study documentation/specs received from developers | 2016.12.08 | 2016.12.09 |
| QA - Test plan creation | 2016.12.12 | 2016.12.16 |
| QA - Test cases/Env preparation | 2016.12.13 | 2016.12.20 |
| QA - Nightly Testing | 2016.12.16 | 2017.01.23 |
| 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/ Google docs |
| Test case execution | TestRail |
| Bugs management | Bugzilla |
Status
Overview
Landed on Nightly - 53.0a1 (2016-11-20) Merged to Aurora on 2017-02-15 Track the dates and build number where feature was merged to Release/Beta
References
- List and links for specs
Media Control Specs - link
- Meta bug 1271765
Testcases
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | Yes | |
| Multi-Process Enabled | Yes | |
| Multi-process Disabled | Yes | |
| Theme (high contrast) | Yes | |
| UI | ||
| Mouse-only operation | Yes | |
| Keyboard-only operation | Yes | |
| Display (HiDPI) | Yes | |
| Interraction (scroll, zoom) | Yes | |
| Usable with a screen reader | Yes | e.g. with NVDA |
| Usability and/or discoverability testing | Yes | Is this feature user friendly |
| RTL build 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) | 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 | No | 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 | No | List of error conditions to monitor |
| 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 | No | |
| Privilege escalation testing | No | |
| Fuzzing | No | |
| Web Compatibility | depends on the feature | |
| Testing against target sites | Yes | |
| 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 - in TestRail at link
Bug Work
Meta bug - 1271765 - Visual refresh of media controls
Logged bugs ( blocking 1271765 )
38 Total; 3 Open (7.89%); 19 Resolved (50%); 16 Verified (42.11%);
Bug fix verification
27 Total; 0 Open (0%); 11 Resolved (40.74%); 16 Verified (59.26%);
Sign off
Criteria
Check list
- All test cases should be executed
- 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
- List of OSes that will be covered by testing: Windows 10 x64, Ubuntu 16.04 x86 and Mac OS X 10.11 (El Capitan)
- Link for the test runs on Nightly - link
- Full Test suite - test suite link
Aurora Testing
- Mid-Aurora sign-off
- List of OSes that will be covered by testing: Windows 10 x64, Windows 7 x64, Ubuntu 16.04 x86 and Mac OS X 10.12.3 Beta (Sierra)
- Link for the tests run - https://testrail.stage.mozaws.net/index.php?/plans/view/2414
- Full Test suite - https://testrail.stage.mozaws.net/index.php?/suites/view/360&group_by=cases:section_id&group_order=asc
- List of OSes that will be covered by testing: Windows 10 x64, Windows 7 x64, Ubuntu 16.04 x86 and Mac OS X 10.12.3 Beta (Sierra)
- Pre-Beta sign-off
- List of OSes that will be covered by testing: Windows 10 x64, Windows 7 x64, Ubuntu 16.04 x64 and Mac OS X 10.12.3 Beta (Sierra)
- Link for the tests run - https://testrail.stage.mozaws.net/index.php?/plans/view/2856
- Full Test suite - https://testrail.stage.mozaws.net/index.php?/suites/view/360&group_by=cases:section_id&group_order=asc
- List of OSes that will be covered by testing: Windows 10 x64, Windows 7 x64, Ubuntu 16.04 x64 and Mac OS X 10.12.3 Beta (Sierra)
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 | [DONE] | Available test for Video Play: https://dxr.mozilla.org/mozilla-central/source/toolkit/content/tests/widgets https://dxr.mozilla.org/mozilla-central/source/accessible/tests/mochitest/actions/test_media.html |
| Performance Testing | N/A | |
| All Defects Logged | [DONE] | |
| Critical/Blockers Fixed and Verified | [DONE] | |
| Metrics/Telemetry | N/A | |
| QA Signoff - Nightly Release | [DONE] | Email sent 01-23-2017 (GREEN) |
| QA Aurora - Mid-Aurora Sign off | [DONE] | Email sent 02-20-2017 (GREEN]) |
| QA Signoff - Pre-Beta Sign off | [DONE] | Email sent 03-03-2017 (GREEN) |
| QA Beta - Full Testing | ||
| QA Signoff - Beta Release | Email to be sent |
