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.
|16/05/2017||1.0||Emil Pasca||Created first draft|
- 1 Overview
- 2 Testing summary
- 3 Requirements for testing
- 4 Test Strategy
- 5 Status
- 6 References
- 7 Testcases
- 8 Bug Work
- 9 Sign off
Firefox Notes is an experiment slated to launch in Firefox Test Pilot in Q2 2017. The MVP is an encrypted notepad in the browser that will allow people using Firefox to document, save, and revisit information without leaving the browser.
This wiki details the testing that will be performed by the project team for the Firefox Notes 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
Ryan Feeley (irc: ryanfeeley)
Feature email address: - email@example.com
Scope of Testing
Help users get more out of the web, by offering a convenient place to save, and revisit information without leaving the browser.
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
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
- Mac OS X 10.12
This section details the progression test objectives that will be covered.
|Ref||Function||Test Objective||Evaluation Criteria||Test Type||Owners|
|1||Install Firefox Notes experiment add-on||Verify that the add-on is correctly installed.||Add-on UI changes are present in browser.||Manual||Eng Team|
|2||Firefox Notes functionality||Verify that the user can store, retrieve notes which will persist even after browser restarts and also can sync between browsers.|| 1. Type in the Notes panel some notes.
2. Use the available text formating options.
3. Open multiple Notes tabs / windows.
|3||Keyboard only navigation||Verify that all add-on functionalities can be accessed from the keyboard.||All functionalities can be accessed from keyboard.||Manual||Eng Team|
|4||Private Browsing||Verify the functionality of the add-on in Private Browsing mode.||TBD||Manual||Eng Team|
|5||Disable / Re-enable Notes||Verify that the add-on can be disabled and enabled without any issues.|| 1. Disable Notes add-on and verify that its extension panel is no longer available.
2. Re-enable Notes add-on and verify that its extension panel is available.
|6||Uninstall Notes add-on||Verify that the menu changes are reverted and browser returns to default.|| 1. Notes add-on is uninstalled.
2. Toolbar icon is removed.
Since Firefox Notes is an add-on, you can install it from the following links:
- From the Firefox Notes GitHub repository by following the building steps. Later you can install the resulted .zip file in "about:addons" page.
- Or you can install it trough Test Pilot experiments page when the experiment will be available.
Note that the add-on only works in Firefox 51+, while Test Pilot requires at least Firefox 50..
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
|Project phase||Start Date||End Date|
|Study documentation/specs received from developers||05/11/2017||-|
|QA - Test plan creation||05/16/2017||05/17/2017|
|QA - Test cases/Env preparation||06/09/2017|
|QA - Pre-Release in Test Pilot Testing|
|QA - Release in Test Pilot Date|
|QA - Nightly Testing|
Detail the tools to be used for testing, for example see the following table:
|Test plan creation||Mozilla wiki|
|Test case creation||TestRail|
|Test case execution||TestRail|
Track the dates and build number where feature was released to Nightly Track the dates and build number where feature was merged to Beta Track the dates and build number where feature was merged to Release
|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.
|Firefox Notes add-on compatibility and usability with e10s/non e10s tabs.||- Firefox Notes add-on should be e10s compatible.|
|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?
- Testing with RTL mode enabled.
- GitHub repository
- Firefox HoverPad WikiPage
- Roadmap - HoverPad TestPilot
- Etherpad coordination page
Meta bug: N/A
Summary of testing scenarios
|Theme (high contrast)||Yes|
|RTL (Right to Left style)||Yes|
|Interaction (scroll, zoom)||Yes|
|Usable with a screen reader||?|
|Usability and/or discoverability testing||Yes||Is this feature user friendly|
|Feature upgrades/downgrades data as expected||Yes|
|Does sync work across upgrades||Yes|
|Requires install testing||Yes|
|Affect first-run or onboarding||?|
|Does this affect partner builds? Partner build testing||Yes||
|Temporary or permanent telemetry monitoring||-||Not on QA manual end.|
|Telemetry correctness testing||-||Not on QA manual end.|
|Server integration testing||-||Not on QA manual end.|
|Offline and server failure testing||-||Not on QA manual end.|
|Load testing||-|| Not on QA manual end.
|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|
|Testing with existing/popular add-ons||Yes||
|3rd-party security review||-||Not on QA manual end.|
|Privilege escalation testing||-||Not on QA manual end.|
|Fuzzing||-|| Not on QA manual end.
|Web Compatibility||depends on the feature|
|Testing against target sites||No|
|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||Yes|
- Full Test suite - TBA
- Smoke Test suite - TBA (if needed)
- Regression Test suite - TBA (if needed)
- Tracking bug – N/A
- Found issues list - Engineering QA found issues
- Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
- All test cases should be executed
- All blockers and critical issues must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/QA)
Link for the tests runs
- Full Test suite
|Testing Prerequisites (specs, use cases)||[DONE]|
|Testing Infrastructure setup|
|Test Plan Creation||[DONE]|
|Test Cases Creation||[IN PROGRESS]|
|Full Functional Tests Execution||[NOT STARTED]|
|Automation Coverage||-||Not on QA manual end.|
|Performance Testing||-||Not on QA manual end.|
|All Defects Logged|
|Critical/Blockers Fixed and Verified|
|Daily Status Report (email/etherpad statuses/ gdoc with results)||-|
|Metrics/Telemetry||-||Not on QA manual end.|
|QA Signoff - Nightly Release||Email to be sent|