QA/One-off Searches From Awesomebar
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 |
Contents
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
Roxana Leitan (irc: RoxanaLeitan) - 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/awesome bar using the already defined search engines. The testing effort for the One-Off Searches Awesomebar will be invested in 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
Other configuration/environmental setup needed:
- In Firefox configuration settings browser.urlbar.oneOffSearches preference needs to be set to true.
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 Upgrade/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 51.0a1: link on 08.04.2016
- 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 | 2017.06.02 |
| QA - Beta Testing | 2017.06.16 | 2017.07.07 |
| Release Date | 2017.07.13 | 2017.07.21 |
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
- Landed on Nightly:
- First Landed on Nightly 51.0a1: link on 08.04.2016
- At merge with Aurora, the feature was not sign-off to Aurora due to a large number of bugs opened on this feature. Feature remains disabled on Aurora 51 and enabled on Nightly 52
- The feature also missed the Firefox 52, 53 and 54 releases, due to the large number of issues, work was re-prioritized in Bug 1337003
Risk analysis
- Awesomebar functionality/performance might be affected by One-off searches buttons from Awesomebar.
References
- Meta bugs:
- List and links for specs
- Useful info about Awesomebar search at link
Testcases
Full test suites can be found on TestRail at link or in the PDF doc (last update made - 2017-06-02)
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 | Yes | 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
Bug Work
Tracking bugs:
Logged bugs ( blocking 1180944 )
59 Total; 1 Open (1.69%); 28 Resolved (47.46%); 30 Verified (50.85%);
Bug Verification (blocking 1180944)
35 Total; 0 Open (0%); 5 Resolved (14.29%); 30 Verified (85.71%);
Logged bugs ( blocking 1337003 )
9 Total; 0 Open (0%); 3 Resolved (33.33%); 6 Verified (66.67%);
Bug Verification (blocking 1337003)
8 Total; 0 Open (0%); 2 Resolved (25%); 6 Verified (75%);
Sign off
Criteria for Mid Nightly
Check list
- All the smoke tests (designed to ensure the main functionality is working as expected) are executed.
Criteria for Pre-Beta Release and Pre-Release
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
Mid Nightly testing
Testing will be performed on folowing OSes
- Windows (Windows 7 or Windows 10)
- Ubuntu 16.04
- Mac OS X
Link for the tests run
- Full Test suite, at link
- Regression Test suite, if needed/available
Pre-Beta testing
Testing will be performed on folowing OSes
- Windows 10 x64
- Ubuntu 16.04 x64
- Mac OS X 10.12
Link for the tests run - One-off searches from Awesomebar - pre-Beta testing - Nightly 55 Links for the test report - link
Pre-Release testing
Testing will be performed on folowing OSes
- Windows 10 x64
- Ubuntu 16.04 x64
- Mac OS X 10.12
Link for the tests run - One-off searches from Awesomebar - pre-Release testing - Beta 55 Links for the test report - link
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 | [DONE] | Covered by test: https://dxr.mozilla.org/mozilla-central/source/browser/base/content/test/urlbar/browser_urlbarOneOffs.js |
| Performance Testing | N/A | |
| All Defects Logged | [IN PROGRESS] | |
| Critical/Blockers Fixed and Verified | [DONE] | |
| Metrics/Telemetry | [DONE] | |
| QA mid-Nightly Signoff | [DONE] | [Email sent in 5/11/2017] |
| QA pre-Beta Signoff | [DONE] | Email sent on June 2nd, 2017 |
| QA Beta - Full Testing | [DONE] | |
| QA pre-Release Signoff | [DONE] | Email sent on 21st July, 2017. |
