QA/New Awesomebar
Contents
Overview
Purpose
The purpose of this wiki is to serve as a general test plan for verifying the new Awesomebar feature.
Scope
The testing will be focus on verifying that the awesomebar works correctly after latest implementation
Testing will be performed manually, by the Desktop QA team.
Ownership
Developer contacts: Drew Willcoxon
QA: Cornel Ionce
Testing Summary
Scope of testing
In Scope
The main testing scope is to assure that the recent changes did not affect the awesomebar functionality.
Requirements for testing
Environments
Testing will be performed on following OSes (both x86 & x64 infrastructures):
- Mac OS X 10
- Windows 7
- Windows 8.1
- Windows 10
- Windows XP
- Ubuntu 14.04
Testing on specific devices is not needed.
Test Strategy
Test Objectives
Following table contains main features to be tested:
Ref | Function | Test Objective | Evaluation Criteria |
---|---|---|---|
1 | |||
2 | |||
3 |
Test Types
Type of Testing | Required (Yes/No) | Owners | Details/Comments |
---|---|---|---|
Manual | Yes | Moz QA Rel team | |
Automation | TBD | ||
Performance | No | ||
Security | No | ||
Usability | No | ||
Metrics/Telemetry | TBD |
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
[LANDED] Nightly 49: first landed on - 2016-04-06
Risk analysis
- No Risks found at the moment
References
Meta: Bug 1181078
Test cases
Overview
The available test cases can be found here
Bugs Work
Tracking bug: Meta bug 1181078
Bug fix verification
Bug No | Summary | Status | Firefox Verion |
---|---|---|---|
1266375 | Suggestions twitch when I edit string in location bar | Verified - Fixed | 48 |
1266374 | First suggestion isn't selected (e.g. can't see the search engine) when I open suggestions via Down key | Verified FIXED | 48 |
1265110 | Make switchToTab2, visit and searchWithEngine address bar autocomplete rows localizable | RESOLVED INVALID | |
1264337 | We lost the sync/tabs-from-other-devices tab icon in the awesomebar popup redesign | Verified FIXED | Firefox 48 |
1263698 | Em dash separator between title and URL/action is incorrectly placed for URLs in RTL in the awesomebar popup | Verified FIXED | Firefox 48 |
1263674 | Awesomebar popup truncates text incorrectly in RTL | Verified FIXED | Firefox 48 |
1262686 | Don't use margin-left on PopupAutoCompleteRichResult with RTL locales | Verified FIXED | Firefox 48 |
1258898 | Allow popups to be partially off-screen | Resolved WFM | Firefox 48 |
1139902 | Breakdown: Implement awesomebar improvements | Resolved Fixed | Firefox 48 |
1074937 | Change the default favicon from an empty dashed-box to a globe | Resolved Fixed | Firefox 48 |
959564 | [UX] Design for awesomebar search suggestions | Resolved Fixed | Firefox 48 |
Logged bugs
Sign off
Criteria
- 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
- [DONE] Full Test suite results [1]
- There were no blockers found while testing this feature.
- Manual testing covered Windows 7, Windows 8.1, Windows 10, Ubuntu 14.04 and Mac OS x 10.11.
[DONE] Merge to Aurora Sign-off (2016-04-12)
[DONE] Mid-Aurora Sign-off (2016-05-20)
- Full Test suite results [2]
- Manual testing covered Windows 8.1 x64, Windows 10x64, Ubuntu 12.04 x86 and Mac OS X 10.9.5.
- There were no new issues found during sign-off.
[DONE] Pre-beta Sign-off (2016-06-01)
- Full Test suite results [3]
- Manual testing covered Windows 8.1 x86, Windows 10x64, Ubuntu 12.04 x86 and Mac OS X 10.9.5.
- There were no new issues found during sign-off.
[DONE] Pre-Release Sign-off (2016-25-07)
- Full Test suite results [4]
- Manual testing covered Windows 8.1 x86, Windows 10x64, Ubuntu 12.04 x86 and Mac OS X 10.9.5.
- Bug 1288120 was filled during the sign-off process, although this is not a regression and not caused by the recent awesomebar changes.