QA/Sync Tabs Sidebar

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
2/15/2016	1.0	Adrian Florinescu	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

Developer contacts: Edwin Wong

QA:
Rares Bologa - PM for QA team

Brindusa Tot - leading QA efforts

Adrian Florinescu, QA

Simona Badau, QA

Ovidiu Boca, QA

Testing summary

Scope of Testing

In Scope

Sync Tabs is a project in Mozilla that aims to ensure your currently open tabs inside Firefox are available via Sync anywhere Firefox is supported. In addition to Sync Tabs, a corresponding sidebar will be added: Sync Tabs Sidebar, similar with Bookmarks/History sidebar. In the scope of our testing is the Sidebar for Sync Tabs and its functionality. The testing effort for SyncTab Sidebar will be invested on the following areas:

• usability: the sybc tab sidebar must be easy to use and straightforward;
• integration: devices and OS : the QA team will ensure no issues are related to synced tabs that come from different devices/OS's combinations;
• functionality: basic and advanced functionality to be verified according to the existing requirements;

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:

• Sync
• History?
• Bookmarks?
• Sync Tabs Sidebar on firefox mobile?

Requirements for testing

Environments

Testing will be performed on following OSes:

• Bulleted list item
• Windows 7
• Windows 10
• Windows XP
• Ubuntu 15.04
• Mac OS X 10

Testing will be done on iOS(iPad) and Android devices.

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 Sync Tabs sidebar	The objective the test is trying to demonstrate that Sync tabs sidebar can be opened from different browser location	Sidebar can be opened from 4 location 1. The View > Sidebar menu 2. The "View Synced Tabs Sidebar" toggle in the menu item 3. The option in the Sidebar toolbar button 4. Keyboard shortcut (to be determined)	Manual	Eng Team
2	Sync Sidebar functionality	The objective of these test suites is to verify that all requirements related to the Sync Sidebar 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	Sync Sidebar usability	The objective of these test suites is to verify that the application is user friendly.	The criteria that will be evaluated to demonstrate the test is successful	Manual/ Usability	Eng Team
4	Sync Sidebar Integration	The objective of these test suites is to ensure that no issues come from using synced tabs with different devices/OS's combinations;	The criteria that will be evaluated to demonstrate the test is successful	Manual	Eng Team
5	Regression testing on the existing logged and fixed Bugzilla bugs	Verify marked as fixed bugs against the Nightly Builds	The criteria that will be evaluated to demonstrate the test is successful	Manual/Regression testing	Eng Team

Builds

This section should contain links for builds with the feature -

• Nightly builds with the fix are available to the the 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	02/15/2016	03/07/2016
Study documentation/specs received from developers	02/15/2016	02/18/2016
QA - Test plan creation	02/16/2016	02/19/2016
QA - Test cases/Env preparation	02/16/2016	02/19/2016
QA - Nightly Testing	02/19/2016	03/07/2016
QA - Aurora Testing	TBD	TBD
QA - Beta Testing	TBD	TBD
Release Date	TBD	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

Track the dates and build number where feature was released to Nightly

• https://archive.mozilla.org/pub/firefox/nightly/2016/01/2016-01-25-06-06-32-mozilla-central/

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

• Sync Tabs Sidebar mocks: link
• Meta bug : bug 1214379

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Private Window	N/A
Multi-Process Enabled	N/A
Multi-process Disabled	N/A
Theme (high contrast)	N/A
UI	Yes
Mouse-only operation	Yes
Keyboard-only operation	No
Display (HiDPI)	No
Interraction (scroll, zoom)	Yes
Usable with a screen reader	N/A	e.g. with NVDA
Usability and/or discoverability testing	Yes	Is this feature user friendly
Help/Support	TBD
Help/support interface required	TBD	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	N/A
Feature upgrades/downgrades data as expected	N/A
Does sync work across upgrades	Yes
Requires install testing	N/A	separate feature/application installation needed (not only Firefox)
Affects first-run or onboarding	N/A	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	N/A	yes/no options, add comment with details about who will lead testing
Enterprise	N/A	Raise up the topic to developers to see if they are expecting to work different on ESR builds
Enterprise administration	N/A
Network proxies/autoconfig	N/A
ESR behavior changes	N/A
Locked preferences	N/A
Data Monitoring	N/A
Temporary or permanent telemetry monitoring	N/A	List of error conditions to monitor
Telemetry correctness testing	N/A
Server integration testing	N/A
Offline and server failure testing	N/A
Load testing	Yes
Add-ons	N/A	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?	N/A
Comprehensive API testing	N/A
Permissions	Yes
Testing with existing/popular addons	No
Security	No
3rd-party security review	No
Privilege escalation testing	No
Fuzzing	No
Web Compatibility	No
Testing against target sites	No
Survey of many sites for compatibility	No
Interoperability	Yes
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	Yes
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

Bug 111111
Bug 211111

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
  • Daily Smoke, use template from link
  • Full Test suite, use template from link
  • Regression Test suite, if needed/available

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)	In Progress
Testing Infrastructure setup	No
Test Plan Creation	In progress
Test Cases Creation	In progress
Full Functional Tests Execution	Not Started
Automation Coverage	N/A
Performance Testing
All Defects Logged	TBD
Critical/Blockers Fixed and Verified
Daily Status Report (email/etherpad statuses/ gdoc with results)
Metrics/Telemetry
QA Signoff - Nightly Release	TBD	Email to be sent
QA Aurora - Full Testing	N/A
QA Signoff - Aurora Release	N/A	Email to be sent
QA Beta - Full Testing	N/A
QA Signoff - Beta Release	N/A	Email to be sent