QA/Screenshots
This is deprecated, moved to: https://wiki.mozilla.org/QA/PageShot54
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/21/2016 | 1.0 | Vlad Bacia | Created first draft |
| 02/28/2017 | 1.1 | Cosmin Muntean | General Updates |
Contents
Overview
Purpose
Page Shot is an experimental Add-on for Firefox that lets you save and share permanent copies of anything on the web.
Scope
This wiki details the testing that will be performed by the project team for the <project name> 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
Engineering - Ian Bicking
Engineering - Donovan Preston
UX - Bram Pitoyo
QA:
PM for QA team - Rares Bologa
Leading QA efforts - Paul Oiegas
QA - Cosmin Muntean
Communication channels:
IRC - #pageshot
Public feedback email - pageshot-feedback@mozilla.com (goes to Ian, Donovan, and Bram)
Testing summary
Scope of Testing
In Scope
Page Shot lets you save anything on the web, including pages that requires a login or content that changes or is personalized. Once you've created a shot, anyone you give the link to can view it; never worry about logins or disappearing content. Page Shot is built and hosted by Mozilla, so you know it's safe to use.
The scope of our testing is the Page Shot-desktop add-on and its functionality. The testing effort for Page Shot will be invested on the following areas:
- integration: verify the add-on integration with the current browser functionalities and UI;
- functionality: basic and advanced functionality to be verified according to the existing requirements;
- usability: Page Shot features must be easy to use and straightforward;
Out of Scope
The mobile implementation and 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 14.04
- Ubuntu 16.04
- Mac OS X 10.10
- Mac OS X 10.11
- Mac OS X 10.12
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 | Evaluation Criteria | Test Type | Owners |
|---|---|---|---|---|---|
| 1 | Install Page Shot add-on | Verify that the add-on is correctly installed. | Add-on UI changes are present in the browser. | Manual | Eng Team |
| 2 | Page Shot functionality | Verify all Page Shot options are working. | 1. Save anything on the web. 2. Share content. |
Manual | Eng Team |
| 3 | Disable / Re-enable Page Shot add-on | Verify that the add-on can be disabled and enabled without any issues. | 1. Disable Page Shot add-on. 2. Verify that the browser UI returned to default functionality on the affected areas. 3. Re-enable Page Shot add-on and verify that the browser has changed back. |
Manual | Eng Team |
| 4 | Uninstall Activity Stream add-on | Verify that the UI changes are reverted and browser returns to default. | 1. Uninstall the Page Shot add-on. 2. Verify that the browser UI returned to default functionality on the affected areas. |
Manual | Eng Team |
Builds
Since Page Shot is an add-on, you can install it from the following links:
Or you can install it trough Test Pilot experiments page, when the experiment will be available.
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
| Project phase | Start Date | End Date |
|---|---|---|
| Start project | 8/02/2015 | - |
| Study documentation/specs received from developers | 07/19/2016 | 07/20/2016 |
| QA - Test plan creation | 07/21/2016 | 07/22/2016 |
| QA - Test cases/Env preparation | 09/01/2016 | 09/09/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 PageShot add-on compatibility and usability with content specific websites | - Pictures and Videos from embedded sources. - Private websites and private content. |
| 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
List and links for specs:
- PageShot Wiki page.
- PageShot Dev website.
- PageShot Production website.
- PageShot GitHub repository.
- PageShot Privacy Statement.
- PageShot Metrics.
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 | No | |
| Display (HiDPI) | Yes | |
| Interraction (scroll, zoom) | Yes | |
| Usable with a screen reader | No | e.g. with NVDA |
| Usability and/or discoverability testing | Yes | Is this feature user friendly |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | Yes | |
| Does sync work across upgrades | Yes | |
| Requires install testing | Yes | |
| Affects first-run or onboarding | No | |
| Does this affect partner builds? Partner build testing | No | We won't have partner builds available for testing in the Nightly or Aurora channels |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | - | Not covered by the Engineering QA team |
| Telemetry correctness testing | - | Not covered by the Engineering QA team |
| Server integration testing | - | Not covered by the Engineering QA team |
| Offline and server failure testing | - | Not covered by the Engineering QA team |
| Load testing | - | Not covered by the Engineering QA team |
| 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 | 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 | - | Not covered by the Engineering QA team |
| Privilege escalation testing | - | Not covered by the Engineering QA team |
| Fuzzing | - | Not covered by the Engineering QA team |
| Web Compatibility | ||
| Testing against target sites | Yes | |
| Survey of many sites for compatibility | No | |
| Interoperability | ||
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | ||
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | No | |
| Interaction of this feature with other browser features | Yes |
Test suite
- Full Test suite - Page Shot Full Functional (TestRail)
- Smoke Test suite - TBD
- Regression Test suite - TBD if available/needed
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 | - | Not on QA manual end. |
| Performance Testing | - | Not on QA manual end. |
| All Defects Logged | [IN PROGRESS] | |
| 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 |
