QA/Min-Vid
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 |
---|---|---|---|
07/11/2016 | 1.0 | Vlad Bacia & Ciprian Muresan | Created first draft |
Contents
Overview
Purpose
Min-Vid is a Firefox add-on which lets you minimize a web video and keep it within the browser window. The video panel stays visible even when you switch tabs, so you can keep watching while you browse.
Scope
This wiki details the testing that will be performed by the project team for the Min-Vid add-on. 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
Sponsor - Wil Clouser (irc: clouserw)
Engineering - Dave Justice (irc: JSON_voorhees)
Engineering - Jared Hirsch (irc: _6a68)
Engineering - Jen Kagan (irc: kaganjd)
QA:
PM for QA team - Rares Bologa (irc: RaresB)
Leading QA efforts - Paul Oiegas (irc: pauloiegasSV)
QA - Ciprian Muresan (irc: cmuresan)
Communication channels:
IRC channel - #min-vid
Feature email address: TBA
Testing summary
Scope of Testing
In Scope
The goal is to experiment with what it means to start to give the user control over the media they are consuming on the web. Users should be able to consume content in whatever form they feel comfortable. In the future we may be exploring these concepts with other forms of media, such as audio or pdfs.
Out of Scope
Following areas/features are considered out of scope and will not be considered as testing zones to be handled in this test plan:
- Mobile testing
Requirements for testing
Environments
Testing will be performed on the following OSes (both x86 & x64 infrastructures):
- Windows 7
- Windows 8.1
- Windows 10
- Ubuntu 15.04
- Ubuntu 16.04
- Mac OS X 10.10
- Mac OS X 10.11
Test Strategy
Test Objectives
This section details the progression test objectives that will be covered.
Ref | Function | Test Objective | Evaluation Criteria | Test Type | Owners |
---|---|---|---|---|---|
1 | Install Min-Vid add-on | Verify that the add-on is correctly installed. | Add-on UI changes are present in the browser. | Manual | Eng Team |
2 | Min-Vid functionality | Verify that the videos can be played through Min-Vid player add-on. | 1. Videos are played with HTML 5 video player through Min-Vid add-on. 2. Play a single video. 3. Verify that ads are displayed. 4. Open consecutively multiple videos in Min-Vid player. |
Manual | Eng Team |
3 | Window and player controls | Verify that all player controls are working as expected. | 1. Check basic controls (Play/Pause/Stop/Volume). 2. Quick seek forward and backward in a short/long video. 3. Change video resolution (?). 4. Redirect to video page. 5. Minimize/Maximize/Close Min-Vid player options. |
Manual | Eng Team |
4 | Keyboard only navigation | Verify that all player controls are working as expected. | 1. Check basic controls (Play/Pause/Stop/Volume). 2. Quick seek forward and backward in a short/long video. 3. Change video resolution (?). 4. Redirect to video page. 5. Minimize/Maximize/Close Min-Vid player options. |
Manual | Eng Team |
5 | Private Browsing | Verify the functionality of the add-on in Private Browsing mode. | The add-on works as expected. | Manual | Eng Team |
6 | Disable / Re-enable Min-Vid add-on | Verify that the add-on can be disabled and enabled without any issues. | 1. Disable Min-Vid add-on. 2. Verify that the context menu changes are reverted and browser returns to default. 3. Re-enable Min-Vid add-on and verify that the browser context menu has the Min-Vid option. |
Manual | Eng Team |
7 | Uninstall Min-Vid add-on | Verify that the context menu changes are reverted and browser returns to default. | 1. Uninstall the Min-Vid add-on. 2. Verify that the browser context menu has returned to default functionality on the affected areas. |
Manual | Eng Team |
Builds
Since Min-Vid is an add-on, you can install it from the following links:
- A custom build can be made using the steps from GitHub repo.
- Add-on Release version. - TBD
- Add-on Development version. - Min Vid dev Test Pilot website version
Or you can install it trough Test Pilot experiments page, when the experiment will be available. Note that the add-on only works on Firefox versions 46.x and up.
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
Project phase | Start Date | End Date |
---|---|---|
Start project | 3/13/2016 | - |
Study documentation/specs received from developers | 7/08/2016 | 7/09/2016 |
QA - Test plan creation | 7/11/2016 | 7/13/2016 |
QA - Test cases/Env preparation | 7/11/2016 | 9/12/2016 |
QA - Nightly Testing | ||
QA - Aurora Testing | ||
QA - Beta Testing | ||
Release in Test Pilot Date | ||
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 | GitHub |
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
Risk analysis
Risk areas | Mitigation |
---|---|
External dependencies on Test Pilot | - We should do an end-to-end test of how we will integrate with the system. - We should determine what our exact requirements are for sample size. - Look into Telemetry as a contingency plan. |
Browser Min-Vid add-on compatibility and usability with content specific websites | - Videos from embedded sources could be played with Min-Vid. - Multiple video sharing platforms (YouTube, Vimeo, etc.) should be supported. |
Reviews: data practices, AMO, legal | - We should be covered by Test Pilot legal agreement so no additional legal review will be needed for MVP; we will not need to get AMO reviews, internal team code reviews will be enough for MVP launch. |
Scope | - Targeting only en-US? - Accessibility requirements == best effort? |
References
Meta bug: N/A
Testcases
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) | Yes | |
UI | ||
Mouse-only operation | Yes | |
Keyboard-only operation | Yes | |
Display (HiDPI) | Yes | |
Interaction (scroll, zoom) | Yes | |
Usable with a screen reader | No | e.g. with NVDA |
Usability and/or discoverability testing | Yes | Is this feature user friendly |
Help/Support | ||
Help/support interface required | TBD | Make sure link to support/help page exist and is easy reachable. |
Support documents planned(written) | TBD | Make sure support documents are written and are correct. |
Install/Upgrade | ||
Feature upgrades/downgrades data as expected | Yes | |
Does sync work across upgrades | N/A | |
Requires install testing | Yes | separate feature/application installation needed (not only Firefox) |
Affects first-run or onboarding | Yes | 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 | 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 | ||
Network proxies/autoconfig | ||
ESR behavior changes | ||
Locked preferences | ||
Data Monitoring | ||
Temporary or permanent telemetry monitoring | ||
Telemetry correctness testing | ||
Server integration testing | ||
Offline and server failure testing | ||
Load testing | ||
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? | ||
Comprehensive API testing | ||
Permissions | ||
Testing with existing/popular addons | Yes | |
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 | ||
Privilege escalation testing | ||
Fuzzing | ||
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. | style="text-align:center;" | |
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | ||
Interaction of this feature with other browser features | Yes |
Test suite
- Full Test suite - Min Vid Full Functional (TestRail)
- Smoke Test suite - Min Vid Smoke Test suite (gdocs)
- Regression Test suite - TBD
Bug Work
- Tracking bug – N/A
- Found issues list - SV QA Engineering found bugs
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
- Daily Smoke - TBA
- Full Test suite - TBA
- Regression Test suite, if needed/available
Merge to Aurora Sign-off
List of OSes that will be covered by testing
- Link for the tests run - N/A
- Full Test suite - N/A
Checklist
Exit Criteria | Status | Notes/Details |
---|---|---|
Testing Prerequisites (specs, use cases) | [DONE] | |
Testing Infrastructure setup | No | |
Test Plan Creation | [DONE] | |
Test Cases Creation | [DONE] | |
Full Functional Tests Execution | [IN PROGRESS] | |
Automation Coverage | ||
Performance Testing | ||
All Defects Logged | ||
Critical/Blockers Fixed and Verified | ||
Daily Status Report (email/etherpad statuses/ gdoc with results) | ||
Metrics/Telemetry | ||
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 |