QA/Turning On Search Suggestions: Difference between revisions
Simona Badau (talk | contribs) |
Simona Badau (talk | contribs) |
||
| Line 169: | Line 169: | ||
= References = | = References = | ||
* Meta bug: | |||
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1344919 1344919 - META - search suggestions and one-off buttons in Awesome Bar] <br /> | |||
* List and links for specs | * List and links for specs | ||
** Useful info about Awesomebar search at [https://support.mozilla.org/en-US/kb/search-suggestions-firefox link] | |||
= Testcases = | = Testcases = | ||
== Test Areas == | == Test Areas == | ||
Revision as of 11:48, 11 May 2017
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 |
|---|---|---|---|
| 05/11/2017 | 1.0 | Simona Badau | 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 <project name> project. 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
Development
Manager: Panagiotis Astithas (irc: past)
Developer contacts: Marco Bonardo (irc: mak)
Engineering Team - Nightly Testing:
Rares Bologa (irc: RaresB) - PM for QA team
Brindusa Tot (irc: brindusat) - leading QA efforts
Simona Badau (irc: simonab) - QA
Testing summary
Scope of Testing
In Scope
Turning On Search Suggestions is a Mozilla feature that aims to enable the search suggestions by default and give the users the possibility to disable them (before Firefox 55, the search suggestions were disabled by default and the users were asked to enable them).
With this feature, a new hint is displayed in the Awesome's bar dropdown informing the users (that had the search suggestions enabled or that ignored the enabling/disabling of them) about the enabling of the search suggestions. The users that had the search suggestions blocked previously, won't see the hint and the search suggestions won't be enabled in their case.
Out of Scope
Testing of other functionalities of the Awesome bar that are not related to the enabling of the search suggestions 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:
- Search suggestions in the Awesome Bar can be enabled/disabled by checking/unchecking the option "Show search suggestions in location bar results" in about:preferences#general.
Test Strategy
Risk Assessment and Coverage
| ID | Description / Threat Description | Covered by Test Objective | Magnitude | Probability | Priority | Impact Score |
|---|---|---|---|---|---|---|
| RAC-1 | Awesomebar and One offs functionality/performance might be affected by the enabling of the search suggestions | TO-1 | 2-Moderate | 1-Unlikely | 3-High | 6 |
| RAC-2 | Enabling the search suggestions by default confuses users because the search suggestions hint not noticeable enough | TO-1 | 3-High | 3-Almost Certain | 3-High | 27 |
| RAC-3 | The search suggestions hint is displayed also to the non targeted users | TO-2 | 2-Moderate | 2-Possible | 3-High | 12 |
| RAC-4 | The search suggestions are enabled also for the non targeted users | TO-2 | 2-Moderate | 2-Possible | 3-High | 12 |
Values:
- Magnitude: 1- Low , 2-Moderate, 3-High
- Probability: 1-Unlikely, 2-Possible, 3-Almost Certain
- Priority: 1 - Low, 2-Medium, 3-High
Impact Score Breakdown:
- An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
- An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
- An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.
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 | RAC | Owners |
|---|---|---|---|---|---|---|
| 1 | Search suggestions hint | Search suggestions hint is displayed for the users that do not have the search suggestions blocked | The hint informing users that search suggestions are enabled is displayed in the Awesome bar drop down just under the URL | Manual | RAC-1, RAC-2, RAC-3 | Eng Team |
| 2 | Search suggestions disabling | Search suggestions in the Awesome Bar can be disabled | Clicking on Change Settings in the search suggestions hint takes you to the about:preferences#general from where search suggestions can be disabled | Manual | Eng Team | |
| 3 | Accessibility | Search suggestions and the hint announcing them being enabled are visible and usable from accessibility point of view | Testing for accessibility includes: - testing using high Contract themes |
Manual | Eng Team | |
| 4 | Upgrade-Downgrade | The search suggestions hint 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 55.0a1 - to be updated after the enabling of the search suggestions is done.
- 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 | 2017.04.04 | TBD |
| Study documentation/specs received from developers | 2017.04.04 | 2017.04.05 |
| QA - Test plan creation | 2017.05.11 | 2017.05.11 |
| QA - Test cases/Env preparation | 2017.04.04 | 2017.04.06 |
| 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 | TestRail/ Google docs |
| Test case execution | TestRail |
| Bugs management | Bugzilla |
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
References
- List and links for specs
- Useful info about Awesomebar search at link
Testcases
Test Areas
| Test Areas | Covered | Details |
|---|---|---|
| Private Window | ||
| Multi-Process Enabled | ||
| Multi-process Disabled | ||
| Theme (high contrast) | ||
| UI | ||
| Mouse-only operation | ||
| Keyboard-only operation | ||
| Display (HiDPI) | ||
| Interaction (scroll, zoom) | ||
| Usable with a screen reader | e.g. with NVDA | |
| Usability and/or discoverability testing | Is this feature user friendly | |
| RTL build testing | ||
| Help/Support | ||
| Help/support interface required | 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 | ||
| Does sync work across upgrades | ||
| Requires install testing | separate feature/application installation needed (not only Firefox) | |
| Affects first-run or onboarding | 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 | 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 | ||
| Network proxies/autoconfig | ||
| ESR behavior changes | ||
| Locked preferences | ||
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | List of error conditions to monitor | |
| Telemetry correctness testing | ||
| Server integration testing | ||
| Offline and server failure testing | ||
| Load testing | ||
| 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? | ||
| Comprehensive API testing | ||
| Permissions | ||
| Testing with existing/popular addons | ||
| 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 | ||
| Privilege escalation testing | ||
| Fuzzing | ||
| Web Compatibility | depends on the feature | |
| Testing against target sites | ||
| Survey of many sites for compatibility | ||
| Interoperability | depends on the feature | |
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | ||
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | ||
| Interaction of this feature with other browser features |
Test suite
Full Test suite - Link to test rail - testcases should be added under Firefox Desktop project link Smoke Test suite - Link with the tests - if available/needed. Regression Test suite - Link with the tests - if available/needed.
Bug Work
Meta bug: 12345 - bug summary
Logged bugs ( blocking 12345 )
| ID | Priority | Component | Assigned to | Summary | Status | Target milestone |
|---|---|---|---|---|---|---|
| 15069 | P3 | Networking | jefft | File type url not correctly parsed and created | VERIFIED | M13 |
1 Total; 0 Open (0%); 0 Resolved (0%); 1 Verified (100%);
Bug fix verification
| ID | Priority | Component | Assigned to | Summary | Status | Resolution | Target milestone |
|---|---|---|---|---|---|---|---|
| 15069 | P3 | Networking | jefft | File type url not correctly parsed and created | VERIFIED | FIXED | M13 |
1 Total; 0 Open (0%); 0 Resolved (0%); 1 Verified (100%);
Sign off
Criteria
Checklist
- 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, link to TestRail - Tests Runs and Results link
- Daily Smoke, if needed/available
- Regression Test suite, if needed/available
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 | ||
| Test Cases Creation | ||
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | ||
| Critical/Blockers Fixed and Verified | ||
| Metrics/Telemetry | ||
| Basic/Core functionality Nightly testing | ||
| QA mid-Nightly Signoff | Email to be sent | |
| QA Nightly - Full Testing | ||
| QA pre-Beta Signoff | Email to be sent | |
| QA Beta - Full Testing | ||
| QA pre-Release Signoff | Email to be sent |