QA/FindToolbarTesting
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 |
|---|---|---|---|
| 06/23/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 Find Toolbar project. Its purpose is to document:
- What will be tested
- How testing will be performed
Ownership
Engineering contact: Mike de Boer
QA:
Rares Bologa - PM for QA team
Brindusa Tot - leading QA efforts
Liviu Cirdei, QA
Testing summary
Scope of Testing
In Scope
Firefox's find toolbar has several usability problems that need to be addressed and redesigned. The most significant updates would be:
- background dims when at least one result is found, highlights, is being more visible
- first result found is displayed in a yellow square, highlighted. Next occurrences of the result are displayed with a white background.
The testing efforts will be invested on the following areas:
- functionality: find toolbar functionality on different web pages(small, large, different web page background, pages with different font size, pdf/txt files testing, etc)
- usability: the find toolbar must be easy to use and straightforward;
- performance: make sure that browser performance is not affected (check-boarding, scrolling)
- accessibility: High Contrast themes, Keyboard operation
Out of Scope
Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.
Requirements for testing
Environments
Full Testing will be performed on:
- Windows 7
- Windows 10
- Ubuntu 15.04
- Mac OS X 10.10
Exploratory/Smoke testing will be performed on
- Windows XP
- Windows 8.1
Specify other configuration/environmental setup needed:
- Preference findbar.modalHighlight set on true will enable new implementation of Find Toolbar. On Nightly channel, this preference is set on true by default.
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 | Access Find Toolbar | The objective the test is trying to demonstrate that Sync tabs sidebar can be opened from different browser locations, using mouse or keyboard | Find Toolbar can be opened from: 1. Edit > Find menu |
Manual | Eng Team |
| 2 | Find Toolbar Functionality | The objective of these test suites is to verify that all requirements related to the Find Toolbar functionality are met and that they are functioning as expected | The criteria that will be evaluated to demonstrate the test is successful | Manual/ Performance/ Usability | Eng Team |
| 3 | Find Toolbar Usability | ||||
| 4 | Find Toolbar Accessibility | ||||
| 5 | Browser Performance while find toolbar is opened | ||||
| 6 | Regression testing on the existing logged and fixed Bugzilla bugs | Verify marked as fixed bugs against the Nightly Builds |
Builds
This section should contain links for builds with the feature:
- Links for Nightly builds - available since 06.10.2016 link
- 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 | 06/22/2016 | |
| Study documentation/specs received from developers | 06/22/2016 | 06/24/2016 |
| QA - Test plan creation | 06/23/2016 | 06/28/2016 |
| QA - Test cases/Env preparation | 06/24/2016 | 06/29/2016 |
| QA - Nightly Testing | 06/28/2016 | |
| 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 | Google docs |
| Test case execution | Google docs |
| Bugs management | Bugzilla |
Status
Overview
First releases to Nightly: 06.10.2015 Nighltly Build 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
Testcases
Testcases can be found at link
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 | ?? | e.g. with NVDA |
| Usability and/or discoverability testing | ?? | 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) | No | Make sure support documents are written and are correct. |
| Install/Upgrade | ||
| Feature upgrades/downgrades data as expected | No | |
| Does sync work across upgrades | No | |
| Requires install testing | No | separate feature/application installation needed (not only Firefox) |
| Affects first-run or onboarding | No | 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 | No | |
| Network proxies/autoconfig | No | |
| ESR behavior changes | ?? | |
| Locked preferences | ?? | |
| Data Monitoring | ||
| Temporary or permanent telemetry monitoring | No | 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 | Yes | |
| Survey of many sites for compatibility | Yes | |
| 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 - Link with the gdoc, follow the format from link Smoke Test suite - Link with the gdoc, follow the format from link Regression Test suite - Link with the gdoc - if available/needed.
Bug Work
Tracking bug – meta bug
Bug fix verification
| Bug No | Summary | Status | Firefox Verion |
|---|---|---|---|
| 123 | bug summary | NEW | Nighly 45 |
Logged bugs
67 Total; 17 Open (25.37%); 24 Resolved (35.82%); 26 Verified (38.81%);
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
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) | ||
| Testing Infrastructure setup | ||
| Test Plan Creation | ||
| Test Cases Creation | ||
| Full Functional Tests Execution | ||
| Automation Coverage | ||
| Performance Testing | ||
| All Defects Logged | ||
| Critical/Blockers Fixed and Verified | ||
| Daily Status Report (email/etherpad statuses/ gdoc with results) | ||
| 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 |