QA/One-off Searches From Awesomebar: Difference between revisions
(→Checklist: Added link to automated test) |
|||
| Line 394: | Line 394: | ||
|- | |- | ||
| Automation Coverage || | | Automation Coverage || | ||
|style="text-align:center;" | | |style="text-align:center;" | Covered by test: https://dxr.mozilla.org/mozilla-central/source/browser/base/content/test/urlbar/browser_urlbarOneOffs.js | ||
|- | |- | ||
| Performance Testing | | Performance Testing | ||
Revision as of 23:23, 26 August 2016
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 |
|---|---|---|---|
| 08/18/2016 | 1.0 | Brindusa Tot | Created first draft |
Overview
Purpose
Detail the purpose of this document. For example:
- The test scope, focus areas and objectives
- The test responsibilities
- The test strategy for the levels and types of test for this release
- The entry and exit criteria
- The basis of the test estimates
- Any risks, issues, assumptions and test dependencies
- The test schedule and major milestones
- The test deliverables
Scope
This wiki details the testing that will be performed by the project team for the One-off searches from Awesomebar feature. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
- Verify that One-Off Searches engine are displayed at bottom of Awesomebar
- Verify that One-Off Searches buttons functions correctly, similar with the ones from Searchbar
Ownership
Development
Manager: Panagiotis Astithas (irc: past)
Developer contacts: Drew Willcoxon (irc: adw)
Engineering Team - Nightly Testing:
Rares Bologa (irc: RaresB) - PM for QA team
Brindusa Tot (irc: brindusat) - leading QA efforts
Simona Badau (irc: simonab) - QA
Liviu Cardei (irc: liviucirdei) - QA
Testing summary
Scope of Testing
In Scope
One-Off Searches From Awesomebar is a Mozilla feature that aims to help users with search directly from location/awsomebar using the already defined search engines. The testing effort for the One-Off Searches Awesomebar will be invested on the following areas:
- functionality: basic and advanced functionality to be verified according to the existing requirements;
- usability: the One-Off Searches from Awesomebar feature must be easy to use and straightforward;
- accessibility: the One-Off Searches from Awesomebar feature can be used with High Contrast Theme, Keyboard only or Screen Reader;
Out of Scope
Testing of other functionalities of Awesome bar are not related to search are not in the interest of testing for this feature.
Requirements for testing
Environments
Full testing will be performed on the following OSes:
- Windows, probably Windows 7 and Windows 10
- Mac OS X
- Ubuntu
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 | One-off searches bar display | One off searches bar is displayed | One off searches bar is displayed at bottom of Awesomebar with all search engines defined by user | Manual | Eng Team |
| 2 | One-off searches bar - search functionality | One off searches buttons functions correctly | All search buttons from One-Off searches bar are working correctly | Manual | Eng Team |
| 3 | Accessibility | One off searches from Awesomebar is visible and usable from accessibility point of view | Testing for accessibility includes: - testing using high Contract themes |
Manual | Eng Team |
| 4 | Upgrade-Downgrade | One off searches from Awesomebar behavior at FF Ugrade/Downgrade | One-Off searches Awesomebar buttons are not lost during FF upgrade/downgrade | Manual | Eng Team |
Builds
This section should contain links for builds with the feature
- Links for Nightly builds: First Landed on Nightly on 08.04.2016
- Links for Aurora builds
- Links for Beta builds
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
| Project phase | Start Date | End Date |
|---|---|---|
| Start project | 2016.08.17 | TBD |
| Study documentation/specs received from developers | 2016.08.17 | 2016.08.18 |
| QA - Test plan creation | 2016.08.18 | 2016.08.23 |
| QA - Nightly Testing | 2016.08.23 | |
| 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
The date and build number when feature was released to Nightly: v51.0a1 /20160804030441 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
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
- Useful info about Awesomebar search at link
Testcases
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | Yes | |
| Multi-Process Enabled | Yes | |
| Multi-process Disabled | No | |
| Theme (high contrast) | Yes | |
| UI | ||
| Mouse-only operation | Yes | |
| Keyboard-only operation | Yes | |
| Display (HiDPI) | Yes | |
| Interraction (scroll, zoom) | Yes | |
| Usable with a screen reader | Yes | e.g. with NVDA |
| Usability and/or discoverability testing | Yes | Is this feature user friendly |
| Help/Support | ||
| Help/support interface required | No | 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 | Yes | |
| Does sync work across upgrades | No | |
| Requires install testing | No | separate feature/application installation needed (not only Firefox) |
| Affects first-run or onboarding | NA | 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 | NA | 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 | No | |
| Network proxies/autoconfig | No | |
| ESR behavior changes | No | |
| Locked preferences | No | |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | ? | List of error conditions to monitor |
| Telemetry correctness testing | No | |
| Server integration testing | No | |
| Offline and server failure testing | No | |
| Load testing | No | |
| 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 | No | |
| 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 | No | |
| Privilege escalation testing | No | |
| Fuzzing | No | |
| 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 | No |
Test suite
Full Test suite - can be found on TestRails at link Regression Test suite - if available/needed.
Bug Work
Tracking bug – meta bug 1180944
Bug fix verification
| Bug No | Summary | Status | Firefox Verion |
|---|---|---|---|
| 123 | bug summary | NEW | Nighly 45 |
Logged bugs
Bug 1297374
Bug 1297627
Bug 1297976
Bug 1297382
Bug 1295458
Bug 1298047
Sign off
Criteria
Check list
- All test cases should be executed
- 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
Testing will be performed on folowing OSes
- Windows 7
- Windows 10
- Ubuntu 14.04
- Mac OS X 10.10
Link for the tests run
- Full Test suite, at link
- 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
- Full Test suite
Checklist
| Exit Criteria | Status | Notes/Details |
|---|---|---|
| Testing Prerequisites (specs, use cases) | [DONE] | |
| Testing Infrastructure setup | [DONE] | |
| Test Plan Creation | [DONE] | |
| Test Cases Creation | [DONE] | |
| Full Functional Tests Execution | [IN PROGRESS] | |
| Automation Coverage | Covered by test: https://dxr.mozilla.org/mozilla-central/source/browser/base/content/test/urlbar/browser_urlbarOneOffs.js | |
| Performance Testing | NA | |
| All Defects Logged | [IN PROGRESS] | |
| Critical/Blockers Fixed and Verified | [IN PROGRESS] | |
| 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 |