QA/Sync Bookmarks
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 |
---|---|---|---|
12/14/2016 | 1.0 | Kanchan Kumari | Created first draft |
Contents
Overview
Purpose
Purpose is to test the functionality of Sync Bookmarks feature
This test plan will cover:
- 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 Sync Bookmarks 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
Mozilla Development
Kit Cambridge - [1]
QA Eng. Softvision Las Vegas
PM for QA team - Rares Bologa (IRC: RaresB)
QA Lead- Kanchan Kumari (IRC: Kanchan_QA)
QA - Grover Wimberly IV (IRC: Grover-QA)
QA - Abe Masresha (IRC: Abe_LV)
QA - Stefan Georgiev (IRC: StefanG_QA)
QA - Justin Williams (IRC: JW_SoftvisionQA)
Testing summary
Scope of Testing
In Scope
Sync bookmarks is a project in Mozilla that aims to ensure your currently synced bookmarks with your Firefox account are accessible on other devices (Laptop, Desktop, Android, iOS). The testing effort for Sync Bookmarks will be focused on the following areas:
- Performance issue of browser with large number of bookmarks
- Syncing/uploading bookmarks to server and download them locally
- Importing and Exporting bookmarks
- usability: the sync bookmarks must be easy to use and straightforward;
- integration: devices and OS : the QA team will ensure no issues are related to synced bookmarks that come from different devices/OS's combinations;
- functionality: basic and advanced functionality to be verified according to the existing requirements;
Out of Scope
Automation will be handled by the developer
Requirements for testing
Environments
Windows, Mac OS, Linux, Android, iOS
Channel dependent settings (configs) and environment setups
about:support
Multiprocess Windows 1/1 (Enabled)
Nightly
Testing will be performed on Nightly
Aurora
Not applicable
Beta
Not applicable
Post Beta / Release
Not applicable
Risk Analysiis
Risk areas | Mitigation |
---|---|
Syncing large number of bookmarks across different devices | Ensure there is no validation error in About Sync |
Changes (add, move, delete) in bookmarks sync correctly (even with interrupted sync) on all devices and there is no orphaned bookmark | Check for any validation error in About Sync |
Different device with different sync engine i.e. Android | Check for any syncing error/missing and incomplete bookmarks on Android and iOS |
General perf and behavior regressions | Testing will focus on new tracker doesn't cause any new issue in bookmarks methods |
Test Strategy
Test Objectives
Verification of Sync Bookmarks functionality across all devices for the same account
Note: Port from testrail
Ref | Function | Test Objective | Evaluation Criteria | Test Type | Owners |
---|---|---|---|---|---|
1 | Basic Sync Scenario | Basic syncing between multiple devices for the same firefox account | Make sure Bookmarks get synced and accessible through other devices on the same account | Manual/Regression | Softvision Eng Team Las Vegas |
2 | Interrupted sync | Check the interrupted sync behavior | Bookmark changes should persist and sync even in case of interrupted syncing | Manual/Regression | Softvision Eng Team Las Vegas |
3 | Deleting Bookmarks | Bookmarks get deleted without any issue | Make sure Bookmarks get deleted from account and shows same on other devices. There is no orphaned bookmarks | Manual/Regression | Softvision Eng Team Las Vegas |
4 | Change at startup | Check the bookmark changes within 10 seconds of openning Firefox | Make sure that Bookmark changes are not missed in the syncing process | Manual/Regression | Softvision Eng Team Las Vegas |
5 | Changes between interrupted sync | Check the bookmark changes after interrupted sync and before consequent sync | Make sure that Bookmark changes are not missed in the syncing process | Manual/Regression | Softvision Eng Team Las Vegas |
6 | Sync through different Fx channel | Check users can switch between Fx 53 and earlier channels | Make sure that Bookmark database schema get upgraded | Manual/Regression | Softvision Eng Team Las Vegas |
7 | Sync through different Android and iOS devices | Check any bookmarks changes sync correctly on Android and iOS | Make sure there are no bookmarks syncing issues for Android and iOS | Manual/Regression | Softvision Eng Team Las Vegas |
8 | Import from HTML export | Check imported bookmarks get treated as new and upload to server | Make sure imported bookmarks get imported to server and sync correctly to all devices | Manual/Regression | Softvision Eng Team Las Vegas |
9 | Restore from backup | Check restoring bookmarks from JSON backup doesn't introduce any curruption | Make sure bookmarks get uploaded to server and sync correctly to all devices | Manual/Regression | Softvision Eng Team Las Vegas |
10 | Delete nested folder | Check deleting a folder get deleted on all devices without orphaning any containing items | Make sure folder and all it's child folder get deleted | Manual/Regression | Softvision Eng Team Las Vegas |
11 | Description and Load in Sidebar | Check changing a bookmark description or setting a bookmark to load in sidebar reflects on other devices | Make sure description and setting to load in sidebar synced correctly to all devices | Manual/Regression | Softvision Eng Team Las Vegas |
12 | Tags | Check tagging and untagging a URL sync all bookmarks with same URL with that tag | Make sure tag/untag of one URL sync across all same URL bookmarks on all devices | Manual/Regression | Softvision Eng Team Las Vegas |
13 | Keywords | Check keyword is associated with URL and any change in keyword would sync to other duplicate URL | Make sure keyword change of duplicate URLs sync correctly to all devices | Manual/Regression | Softvision Eng Team Las Vegas |
Builds
This section should contain links for builds with the feature -
- Links for Nightly builds https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
Test Execution Schedule
The following table identifies the anticipated testing period available for test execution.
Project phase | Start Date | End Date |
---|---|---|
Start project | ||
Study documentation/specs received from developers | ||
QA - Test plan creation | 12/14/2016 | |
QA - Test cases/Env preparation | 12/21/2016 | |
QA - Nightly 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 Aurora Track the dates and build number where feature was merged to Release/Beta
References
- Meta bug 1258127
- List of Sync bugs
Bugs | Status |
---|---|
1228827 | New |
1122834 | New |
1301622 | New |
1309930 | New |
1313890 | New |
1274108 | Resolved:Fixed |
1274496 | Resolved:Fixed |
1277983 | Resolved:Fixed |
1285408 | Resolved:Fixed |
1295521 | Resolved:Fixed |
1302901 | Resolved:Fixed |
1314084 | Resolved:Fixed |
1235269 | Resolved:Duplicate of 1258127 |
1269904 | Resolved:WFM |
1295520 | Resolved:Duplicate of 1199077 |
Testcases
Overview
Bookmarks get synced properly to Firefox account and can be accessible from any other device. There should not be any missing bookmarks/orphaned bookmarks.
Test Areas
Test Areas | Covered | Details |
---|---|---|
Private Window | Yes | |
Multi-Process Enabled | Yes | |
Multi-process Disabled | Yes | |
Theme (high contrast) | TBD | |
UI | ||
Mouse-only operation | Yes | |
Keyboard-only operation | Yes | |
Display (HiDPI) | NA | |
Interraction (scroll, zoom) | NA | |
Usable with a screen reader | NA | e.g. with NVDA |
Usability and/or discoverability testing | Yes | Is this feature user friendly |
RTL build testing | Yes | |
Help/Support | ||
Help/support interface required | NA | Make sure link to support/help page exist and is easy reachable. |
Support documents planned(written) | TBD | Make sure support documents are written and are correct. |
Install/Upgrade | ||
Feature upgrades/downgrades data as expected | TBD | |
Does sync work across upgrades | Yes | |
Requires install testing | NA | separate feature/application installation needed (not only Firefox) |
Affects first-run or onboarding | NA | . |
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 | NA | |
Network proxies/autoconfig | NA | |
ESR behavior changes | NA | |
Locked preferences | Yes | |
Data Monitoring | ||
Temporary or permanent telemetry monitoring | NA | List of error conditions to monitor |
Telemetry correctness testing | NA | |
Server integration testing | NA | |
Offline and server failure testing | NA | |
Load testing | NA | |
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? | YES | |
Comprehensive API testing | NA | |
Permissions | NA | |
Testing with existing/popular addons | Yes | |
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 | NA | |
Privilege escalation testing | NA | |
Fuzzing | NA | |
Web Compatibility | Yes | depends on the feature |
Testing against target sites | NA | |
Survey of many sites for compatibility | NA | |
Interoperability | depends on the feature | |
Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. | NA | |
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS | Yes | |
Interaction of this feature with other browser features | Yes |
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 https://bugzilla.mozilla.org/show_bug.cgi?id=1258127
Logged bugs
Bug 1274108
Bug1274496
Bug1277983
Bug1285408
Bug1295521
Bug1302901
Bug1314084
Bug1235269
Bug1269904
Bug1295520
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 and critical bugs 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) | Done | |
Testing Infrastructure setup | TBD | |
Test Plan Creation | Done | |
Test Cases Creation | TBD | |
Full Functional Tests Execution | TBD | |
Automation Coverage | NA | |
Performance Testing | NA | |
All Defects Logged | TBD | |
Critical/Blockers Fixed and Verified | TBD | |
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 |