QA/Universal Search
Revision Histsory
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/25/2016 | 1.0 | Cosmin Muntean | Created first draft |
| 02/27/2017 | 1.1 | Cosmin Muntean | General and Test Pilot EOL updates |
Contents
Overview
The Universal Search experiment graduated from Test Pilot in 11/30/2016 (details here). Has not reached any of the Firefox channels, due to the fact that the project has ended.
The experimental add-on was automatically uninstalled when he graduated from Test Pilot.
Purpose
Universal Search is a Firefox add-on that unifies the search access points in Firefox in order to offer a deeper, more engaging search experience by making local results richer and by including results from the best of the web.
Scope
This wiki details the testing that will be performed by the project team for the Universal Search 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
Ownership
Senior Engineer - Chuck Harmston (irc: chuck)
Product Manager - Nick Chapman (irc: nchapman)
Senior UX Designer - Bryan Bell
Engineering - Jared Hirsch (irc: _6a68)
QA:
PM for QA team - Rares Bologa (irc: RaresB)
Leading QA efforts - Paul Oiegas (irc: pauloiegasSV)
QA - Cosmin Muntean (irc: CosminMCG)
Communication channels:
IRC channel - #universal-search
Feature email address: - testpilot-dev@mozilla.org
Testing summary
Scope of Testing
In Scope
The goal is to verify that the add-on is correctly installed, the UI changes accordingly and the new functionality is present in 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
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 Universal Search add-on | Verify that the add-on is correctly installed. | Add-on UI changes are present in the browser. | Manual | Eng Team |
| 2 | Universal Search | Verify that when typing in the Awesome Bar a dropdown list with recommendations and suggestions sites is displayed. | 1. Verify that the search bar is highlighted when opening a new tab. 2. Typing in the search field correctly works. 3. Verify that the suggestion dropdown is displayed correctly. 4. Hover the suggestions dropdown works properly. 5. Verify that a search is successfully performed. |
Manual | Eng Team |
| 3 | Keyboard only navigation | Check if the keyboard navigation correctly works within the unified awesomebar. | 1. Check if the keys combination works for Awesome Bar. 2. Verify that keys navigation works in the suggestion dropdown list. 3. Verify that a search can be performed using only the keyboard. |
Manual | Eng Team |
| 4 | Default Search Engine | Verify that the default Search Engine is working as expected. | 1. Verify that the default Search Engine is used for performed searches. 2. Verify that the default Search Engine can be changed. 3. Verify that a search is performed with the changed default Search Engine. |
Manual | Eng Team |
| 5 | Private Browsing | Verify the functionality of the add-on. | The add-on works as expected. | Manual | Eng Team |
| 6 | Disable / Re-enable Universal Search add-on | Verify that the add-on can be disabled and enabled without any issues. | 1. Disable Universal Search add-on. 2. Verify that the browser search has returned to default functionality (address + search bar at the top of the browser). 3. Re-enable Universal Search add-on and verify that the address + search bar at the top of the browser are unified. |
Manual | Eng Team |
| 7 | Uninstall Universal Search add-on | Verify that the search bar changes are reverted and browser returns to default. | 1. Uninstall the Universal Search add-on. 2. Verify that the browser search has returned to default functionality (address + search bar at the top of the browser). |
Manual | Eng Team |
Builds
Since Universal Search 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 Development version - No longer available due to graduation from Test Pilot (11/30/2016). You can read the graduation report on Test Pilot experiment page.
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
| Project phase | Start Date | End Date |
|---|---|---|
| Start project | 02/09/2016 | 11/30/2016 |
| Study documentation/specs received from developers | 07/25/2016 | 07/26/2016 |
| QA - Test plan creation | 07/26/2016 | 07/27/2016 |
| QA - Test cases/Env preparation | 07/29/2016 | 08/03/2016 |
| QA - Nightly Testing | - | - |
| QA - Aurora Testing | - | - |
| QA - Beta Testing | - | - |
| Release in Test Pilot Date | 05/10/2016 | 11/30/2016 |
| 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 |
| Test case execution | TestRail |
| Bugs management | GitHub |
Status
Overview
The Universal Search experiment graduated from Test Pilot in 11/30/2016 (details here). Has not reached any of the Firefox channels, due to the fact that the project has ended. The experimental add-on was automatically uninstalled when he graduated from Test Pilot.
Risk analysis
| Risk areas | Mitigation |
|---|---|
| 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. |
| The unified address + search bar may be a bad impact on users | The new functionality has a single bar and this can confuse / annoy the users who are used with both address + search bar |
References
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 |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | Yes | |
| Does sync work across upgrades | Yes | Tested if data is kept after upgrade or after import / sync profile data. |
| Requires install testing | Yes | The add-on can be installed through Test Pilot or trough ".xpi" file. |
| 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 |
| Data Monitoring | ||
| 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 | ||
| Addon API required? | No | |
| Comprehensive API testing | No | |
| Permissions | No | |
| Testing with existing/popular addons | Yes | |
| Security | ||
| 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 | ||
| Testing against target sites | No | |
| Survey of many sites for compatibility | No | |
| Interoperability | ||
| 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 |
Test suite
- Full Test suite - Universal Search Full Functional (TestRail)
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
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 | [NOT STARTED] | |
| Automation Coverage | No | Not on QA manual end. |
| Performance Testing | No | Not on QA manual end. |
| All Defects Logged | [DONE] | |
| 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 | - | No Sign off done. The project has ended. |
