QA/Application Update UI

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
11/16/2016	1.0	Kanchan Kumari	Created first draft

Overview

Purpose

• To test Firefox Application Update UI feature.

Scope

• This wiki details the testing that will be performed by project team for Firefox Application Update UI feature. It defines the overall testing requirements and provides an integrated view of the project test activities. The purpose is to document:

What will be Tested:

• inform the user, when update is available for Firefox and when it is ready to restart
• Different options to update Firefox
• Update failures due to various reasons
• Application Update UI interference with Addons

• How testing will be performed:

Manual Testing

Ownership

Mozilla Development
Robert Strong]

QA Eng. Softvision Las Vegas
Stefan Georgiev - Team Lead ]
Kanchan Kumari - Test Lead
Abe Masresha
Grover Wimberly IV
Justin Williams

Testing summary

Scope of Testing

In Scope

This feature will be tested manually on Windows, Mac OS X and Linux operating systems

Out of Scope

Android and iOS devices

Requirements for testing

Environments

Windows 8.1
Windows 10
Windows 7
Windows XP
Ubuntu/Linux
Mac OS X 10.12

Channel dependent settings (configs) and environment setups

Nightly

Aurora

Beta

Post Beta / Release

Risk Analysiis

Risk areas
User can be running older version (out of date) of Firefox for many reasons: update orphaning (updater is broken, or some 3rd party is interfering with updates), or they have turned off automatic updates

Test Strategy

Test Objectives

Verification of Application Update UI functionality to inform users to update their old Firefox version.

Note: Port from Testrail

Ref	Function	Test Objective	Evaluation Criteria	Test Type	Owners
1	Application Update UI functionality	To test Application Update UI functionality for informing the user if new update is available	Make sure users get prompts to update their old Firefox version	Manual	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	11/16/2016
QA - Test cases/Env preparation
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/ Google docs
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 893505

Testcases

Overview

Websites respond properly to mouse, keyboard, pen/stylus, finger with touch enabled Long pressing to do text selection, menus, scrolling and dragging etc with fingers, stylus and mouse

Test Areas

Test Areas	Covered	Details
Private Window
Multi-Process Enabled	To be tested
Multi-process Disabled
Theme (high contrast)
UI
Mouse-only operation
Keyboard-only operation
Display (HiDPI)
Interraction (scroll, zoom)
Usable with a screen reader		e.g. with NVIDA
Usability and/or discoverability testing		Is this feature user friendly
RTL build testing
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
Does sync work across upgrades
Requires install testing		separate feature/application installation needed (not only Firefox)
Affects first-run or onboarding		.
Does this affect partner builds? Partner build 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		List of error conditions to monitor
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
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
Survey of many sites for compatibility
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

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=893505

Bug fix verification

Bug No	Summary	Status	Firefox Verion
		NEW	Nighly

Logged bugs

TBD

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
  • 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)
Testing Infrastructure setup
Test Plan Creation	In Progress
Test Cases Creation
Full Functional Tests Execution
Automation Coverage	NA
Performance Testing	NA
All Defects Logged
Critical/Blockers Fixed and Verified
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