QA/Tab Center

From MozillaWiki
< QA
Jump to: navigation, search

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
07/12/2016 1.0 Emil Pasca Created first draft

Overview

Purpose

Tab Center is an attempt to solve some of the issues that have emerged from the way people use tabs (most notably the “too many tabs” problem) and provide a more versatile UI basis for future innovation. The first version of this Firefox add-on arranges tabs in a vertical rather than horizontal fashion. It is heavily inspired by and borrows ideas from the excellent VerticalTabs add-on.

Scope

This wiki details the testing that will be performed by the project team for the Tab Center 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

Sponsor - Philipp Sackl
UX - Blake Winton (IRC: bwinton)
UX - John Gruen (IRC: jgruen)
UR - Amelia Abreu
Product - Javaun Moradi (IRC: javaun)
Program - Cory Price (IRC: ckprice)
Engineering - Jared Hirsch (IRC: _6a68)
Engineering - Chuck Harmston (IRC: chuck)
Engineering - Wil Clouser (IRC: clouserw)


QA:
PM for QA team - Rares Bologa (IRC: RaresB)
Leading QA efforts - Paul Oiegas (IRC: pauloiegasSV)
QA - Emil Pasca (IRC: emilpasca)


Communication channels:
IRC channel - #tabcenter
Feature email address: TBA

Testing summary

Scope of Testing

In Scope

The goal is to solve some of the issues that have emerged from the way people use tabs (most notably the “too many tabs” problem) and provide a more versatile UI basis for future innovation. Tab Center moves your tabs to the side of your browser window so they're out of sight when you don't need them, and easy to expand and grab when you do.

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:

- Mobile testing

Requirements for testing

Environments

Testing will be performed on the following OSes (both x86 & x64 infrastructures):

  • Windows 7
  • Windows 8.1
  • Windows 10
  • Ubuntu 15.04
  • Ubuntu 16.04
  • Mac OS X 10.10
  • Mac OS X 10.11

Test Strategy

Test Objectives

This section details the progression test objectives that will be covered.

Ref Function Test Objective Evaluation Criteria Test Type Owners
1 Install Tab Center add-on Verify that the add-on is correctly installed. Add-on UI changes are present in the browser. Manual Eng Team
2 Tab Center functionality Verify that the are now displayed in the vertical tab. 1. You can add a new tab using the "+" button.
1. When a tab is clicked the content of that website is displayed in the current window.
3. Close an existing tab using "x".
4. Verify that the tabs displayed correctly.
5. Open multiple tabs until the vertical scroll bar appears and that you can scroll down and open any tab. 		Manual Eng Team
3 Pin button functionality Verify that the vertical tab is displayed correctly. 1. If the pin icon is enabled, the vertical tab doesn't resize when the cursor leaves the area.
2. When pin icon is disabled, the vertical tab resizes to a narrower version when the cursor leaves the area. 		Manual Eng Team
4 Private Browsing Verify the functionality of the add-on. The add-on works as expected. Manual Eng Team
5 Disable / Re-enable Tab Center add-on Verify that the add-on can be disabled and enabled without any issues. 1. Disable Tab Center add-on.
2. Verify that the browser UI have returned to default functionality on the affected areas.
3. Re-enable Tab Center add-on and verify that the browser has changed back to the Tab Center vertical tabs UI. 		Manual Eng Team
6 Uninstall Tab Center add-on Verify that the context menu changes are reverted and browser returns to default. 1. Uninstall the Tab Center add-on.
2. Verify that the browser UI have returned to default functionality on the affected areas. 		Manual Eng Team

Builds

Since Tab Center is an add-on, you can install it from the following links:

You can install the development version of the add-on by doing the next steps: 1. Download a copy of the github repo as zip and extract in a folder.
2. Navigate to about:debugging page in Firefox.
3. Click the "Load Temporary Add-on" button and pick the install.rdf file from the repository extracted folder.

Or you can install Tab Center trough Test Pilot experiments page, where the experiment is available. Note that the add-on only works on Firefox versions 46.x and up.

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase Start Date End Date
Start project 2/27/2016 -
Study documentation/specs received from developers 7/11/2016 7/12/2016
QA - Test plan creation 7/12/2016 7/15/2016
QA - Test cases/Env preparation 7/29/2016 8/03/2016
QA - Nightly Testing 7/20/2016 -
QA - Aurora Testing
QA - Beta Testing
Release in Test Pilot Date 05/10/2016 -
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
Test case execution TestRail
Bugs management GitHub

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

Risk analysis

Risk areas Mitigation
External dependencies on Test Pilot - We should do an end-to-end test of how we will integrate with the system.
- We should determine what our exact requirements are for sample size.
- Look into Telemetry as a contingency plan.
Accessibility issues - Using the `zoom` functions in the browser may alter the clarity of content and screen reader compatibility.

References

List and links for specs:

Meta bug: N/A

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas Covered Details
Private Window Yes
Multi-Process Enabled Yes
Multi-process Disabled Yes
Theme (high contrast) Yes
UI
Mouse-only operation Yes
Keyboard-only operation Yes
Display (HiDPI) Yes
Interaction (scroll, zoom) Yes
Usable with a screen reader No e.g. with NVDA
Usability and/or discoverability testing Yes Is this feature user friendly


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 Yes
Does sync work across upgrades N/A
Requires install testing Yes separate feature/application installation needed (not only Firefox)
Affects first-run or onboarding Yes
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
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 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
Privilege escalation testing
Fuzzing


Web Compatibility depends on the feature
Testing against target sites No
Survey of many sites for compatibility No
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 Yes

Test suite

  • Full Test suite - TestRail link
  • Smoke Test suite - TBA
  • Regression Test suite - TBA if available/needed.

Bug Work

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 - TBA
    • Full Test suite - TBA
    • Regression Test suite - TBA if needed/available

Merge to Aurora Sign-off List of OSes that will be covered by testing

  • Link for the tests run - N/A
    • Full Test suite - N/A

Checklist

Exit Criteria Status Notes/Details
Testing Prerequisites (specs, use cases) [DONE]
Testing Infrastructure setup No
Test Plan Creation [DONE]
Test Cases Creation [DONE]
Full Functional Tests Execution [IN PROGRESS]
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
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Tab_Center&oldid=1150732"