QA/NoMore404s
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 | Ciprian Muresan | Created first draft |
Overview
Purpose
Link rot (https://en.wikipedia.org/wiki/Link_rot) happens. The problem is that web sites come, and many go. When this happens unsuspecting web surfers can encounter the equivalent of a dead-end sign with little or no suggested next steps. The solution: Detect and intersect 404 conditions. Add functionality to the Firefox browser to check to see if content from the requested URL has been archived, and is available, via the Wayback Machine and, if it is available, offer to render it.
Scope
This wiki details the testing that will be performed for the NoMore404s feature. It defines the overall testing requirements and provides an integrated view of the project test activities.
Ownership
Engineering - [mailto: jgruen@mozilla.com John Gruen] (irc: jgruen)
QA:
PM for QA team - Rares Bologa (irc: RaresB)
Leading QA efforts - Paul Oiegas (irc: pauloiegasSV)
QA - Ciprian Muresan (irc: cmuresan)
Communication channels:
IRC - TBA
Feature email address: TBA
Testing summary
Scope of Testing
In Scope
The goal is to give the User a way to see pages that are no longer available (404 - Page not found.) Verify that inactive pages (404 Page not found) will redirect the user to an archived version of the site (if it exists), if the add-on is installed.
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
- Active Websites
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 the NoMore404s add-on | Verify that the add-on is correctly installed. | Verify that the add-on can be found in about:addons, Extensions section. | Manual | Eng Team |
| 2 | NoMore404s functionality | Verify that the feature works. | Visit a page that is no longer active. | Manual | Eng Team |
| 3 | Private Browsing | Verify that the feature works while in private browsing. | Visit a page that is no longer active. | Manual | Eng Team |
| 4 | Availability | Verify the availability of the add-on. | 1. Active pages do not redirect to archived pages. 2. Inactive pages which result in 404 will redirect to an archived version of the page. |
Manual | Eng Team |
| 5 | Disable NoMore404s | Disable the add-on from about:addons. | Visiting pages that are no longer active show the “404 Page not found” error. | Manual | Eng Team |
| 6 | Uninstall NoMore404s add-on | Remove the add-on from about:addons. | Visiting pages that are no longer active show the “404 Page not found” error. | Manual | Eng Team |
Builds
Since NoMore404s 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. - No More 404s Test Pilot Dev 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 45.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/06/2016 | - |
| Study documentation/specs received | 7/20/2016 | 7/21/2016 |
| QA - Test plan creation | 7/21/2016 | 7/22/2016 |
| QA - Test cases/Env preparation | 7/27/2016 | 9/02/2016 |
| QA - Nightly Testing | ||
| QA - Aurora Testing | ||
| QA - Beta Testing | ||
| Release in Test Pilot Date | ||
| Release Date |
Testing Tools
| 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 | The add-on is installed through Test Pilot |
| External dependencies on the Internet Archive Wayback Machine | Pages that are not archived will here will still have the generic 404 error |
References
List and links for specs:
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 | N/A | |
| Does sync work across upgrades | No | Not relevant |
| 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 |
| 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. | ||
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | ||
| Interaction of this feature with other browser features | Yes |
Test suite
- Full Test suite - NoMore404s Full Functional (TestRail)
- Smoke Test suite - TBD
- Regression Test suite - TBD if 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
- Link for the tests run
- Daily Smoke suite - TBA
- Full Test suite - TBA
- Regression Test suite - TBA if needed/available
Merge to Aurora Sign-off
- 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 | N/A | |
| 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 |