Add-ons/QA/Testplan/Improve keyboard shortcut support: Difference between revisions
| Line 48: | Line 48: | ||
QA Lead: [mailto:vcarciu@softvision.ro Victor Carciu]; irc nick :victorc<br /> | QA Lead: [mailto:vcarciu@softvision.ro Victor Carciu]; irc nick :victorc<br /> | ||
Webextensions QA: [mailto:cosmin.badescu@softvision.ro Cosmin Badescu]; irc nick :CosminB<br /> | Webextensions QA: [mailto:cosmin.badescu@softvision.ro Cosmin Badescu]; irc nick :CosminB<br /> | ||
= Requirements for testing = | = Requirements for testing = | ||
Latest revision as of 09:46, 14 February 2019
Revision History
| Date | Version | Author | Description |
|---|---|---|---|
| 01/29/2018 | 1.0 | Cosmin Badescu | Created first draft |
Overview
Allow the user to understand what the current keyboard mapping is, highlighting keyboard mappings that are overriden by add-ons, and providing a UI for users to adjust keyboard shortcuts used by web extensions.
Purpose
This document purports to detail the test approach for the improvements of Local Storage API and includes Entry/Exit criteria, Scope for testing, links to test cases etc
Entry Criteria
- QA has access to all the PRDs, mocks and related documents
- The feature has landed on Nightly
- AMO parts has landed on dev
Exit Criteria
- All the bugs against the feature have been triaged
- All the P1/P2 bugs have been fixed
- All the resolved bugs have been verified by QA
- The find/fixed rate is going down over a predefined period of time
Acceptance Criteria
This section broadly outlines when the product is ready to ship
- QA has signed off
- All the required Telemetry is in place
- All info is localized at least for a pre-defined set of locales
- All the necessary PR/blogposts have been sent out
Scope
This section describes what parts of the feature will be tested and what parts won't be.
what's in scope?
- The assigned shortcut keys work as expected when they are assigned from the extension.
what's out of scope?
- Security testing
Ownership
Dev Lead: Mark Striemer; irc nick :mstriemer
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Webextensions QA: Cosmin Badescu; irc nick :CosminB
Requirements for testing
Environments
OSes covered: Windows, Mac OS X, Linux
Channel dependent settings (configs) and environment setups
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 | Test Type | Owners |
|---|---|---|---|---|
| TO-1 | Installing from AMO | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
| TO-2 | Installing from local files | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
| TO-3 | Add-on updates | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
| TO-4 | Sideloading | To verify that the extension uses the API correctly | Manual | Add-ons QA Team |
Builds
This section should contain links for builds with the feature -
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 | ||
| QA - Test plan creation | 01-29-2018 | |
| QA - Test cases/Env preparation | 12-15-2018 | N/A |
| QA - Nightly 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 | [ Docs] / [ TestRail] |
| Test case execution | [ Docs] / [ TestRail] |
| Bugs management | Bugzilla / 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 Release/Beta
Risk analysis
Identify the high-risk assumptions Identify existing bugs on the feature with high risk Identify if other areas are affected by the fix
References
* List and links for specs PRD - [1] Install flow - [2]
* bug 1215061 - [META] Better keyboard shortcut support
16 Total; 12 Open (75%); 2 Resolved (12.5%); 2 Verified (12.5%);
* bug 1303384 - UI for re-assigning an extension's command shortcut
13 Total; 2 Open (15.38%); 2 Resolved (15.38%); 9 Verified (69.23%);
Testcases
Overview
Summary of testing scenarios
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Installing from AMO | ||
| Installing from local files | ||
| Installing from thirdparty | ||
| Add-on updates | ||
| Sideloading | ||
| Other |
Test suite
- Link for the [ Initial test planning]
- Link for the [ Google doc tests]
- Link for the Improve keyboard shortcut support
Bug Work
Tracking bug - []
Bug fix verification
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
- Full Test suite, use template from []
Merge to Beta 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 | 05-22-2018 | |
| Test Cases Creation | 05-21-2018 | N/A |
| 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 Beta - Full Testing | ||
| QA Signoff - Beta Release | Email to be sent |