QA/Flash SHIELD Experiment
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 | Stefan Georgiev | Created first draft |
Overview
Purpose
Most of the browsers are planning to move to click-to-activate (CTA). But before Firefox prepare for this shift, we want to understand the impact on the user and the approach we should take.
Scope
This wiki details the testing that will be performed by the project team for the Flash SHIELD Experiment project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
- Goals
Block Flash by default Keep users secure from Flash exploits
- How testing will be performed
Manual
Ownership
Mozilla Development
QA Eng. Softvision Las Vegas
Stefan Georgiev - Team Lead
Grover Wimberly IV - Tester
Kanchan Kumari - Tester
Abe Masresha - Tester
Justin Williams - Tester
Testing summary
Scope of Testing
In Scope
This feature will be tested manually on Windows, OSX and Linux operating systems.
Out of Scope
Android & iOS Devices
Requirements for testing
Environments
Windows 7
Windows 8.1
Windows 10
Ubuntu/Linux
Macintosh 10.12
Channel dependent settings (configs) and environment setups
Post Beta / Release
Not Applicable
Test Strategy
Test Objectives
Verify Camera and Microphone
Verify Screen Sharing (Single/Dual Monitors) [Cisco Spark]
Verify Application Sharing
Verify Window Sharing
Builds
- Links for Nightly builds:
- Latest Mozilla Central Nightly Builds [[1]]
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
| Project phase | Start Date | End Date |
|---|---|---|
| Start project | ||
| Study documentation/specs received from developers | 10/24/2016 | |
| QA - Test plan creation | 10/27/2016 | |
| QA - Test cases/Env preparation | 10/25/2016 | |
| QA - Nightly Testing | ||
| 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
Track the dates and build number where feature was released to Nightly TBD
Risk analysis
Accidental exposure -> sharing information on the desktop not intended to share
References
- Meta bug
Testcases
Overview
Summary of testing scenarios
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | Certain tests are performed in a private window. | |
| Multi-Process Enabled | Enabled by default | |
| Multi-process Disabled | Only tested if there are bugs found in testing | |
| Theme (high contrast) | Not applicable | |
| UI | ||
| Mouse-only operation | To be tested | |
| Keyboard-only operation | To be tested | |
| Display (HiDPI) | To be tested | |
| Interraction (scroll, zoom) | To be tested | |
| Usable with a screen reader | e.g. with NVDA | |
| Usability and/or discoverability testing | Is this feature user friendly | |
| RTL build testing | To be tested | |
| Help/Support | ||
| Help/support interface required | Make sure link to support/help page exist and is easy reachable. | |
| Support documents planned(written) | Make sure support documents are written and are correct. | |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | Not applicable | |
| Does sync work across upgrades | Not applicable | |
| Requires install testing | Default installation with Nightly | |
| Affects first-run or onboarding | 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 | Not applicable | |
| Network proxies/autoconfig | Not applicable | |
| ESR behavior changes | Not applicable | |
| Locked preferences | Not applicable | |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | List of error conditions to monitor | |
| Telemetry correctness testing | Not applicable | |
| Server integration testing | Not applicable | |
| Offline and server failure testing | Not applicable | |
| Load testing | Not applicable | |
| 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? | Not applicable | |
| Comprehensive API testing | Not applicable | |
| Permissions | Permission manager for sharing microphone, camera, and screen/monitor. | |
| Testing with existing/popular addons | Not applicable | |
| 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 | Not applicable | |
| Privilege escalation testing | Not applicable | |
| Fuzzing | Not applicable | |
| Web Compatibility | depends on the feature | |
| Testing against target sites | CiscoSpark, Skype, GoToMeeting, free web communication services | |
| Survey of many sites for compatibility | Not applicable | |
| Interoperability | depends on the feature | |
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | Some tests require 2+ people to be able to do | |
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | Desktop only | |
| Interaction of this feature with other browser features | Possible testing with other browsers |
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
Tracking bug – meta bug
Bug fix verification
| Bug No | Summary | Status | Firefox Verion |
|---|---|---|---|
| [TBA] | bug summary | NEW | Nightly |
Logged 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
Merge to Aurora Sign-off
List of OSes that will be covered by testing
- Link for the tests run
- Full Test suite
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | ||
| Testing Infrastructure setup | ||
| Test Plan Creation | ||
| Test Cases Creation | ||
| Full Functional Tests Execution | ||
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | ||
| Critical/Blockers Fixed and Verified | ||
| 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 |