QA/Photon Visual Redesign

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
05/09/2015	1.0	Brindusa Tot	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 Photon Visual Redesign 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

Followings will be included into the new the way Firefox looks and make it feel fast and modern:

• Update and Refine Visual Language
• Update or remove heavy stylistic elements
• Streamline layout
• Explore More Distinctive Visuals
• Be Smart About Being a Good Platform Citizen
• Modernize

Ownership

Engineering lead
  Justin Dolske

Engineering Team
  Dao Gottwald
  Nihanth Subramanya
  Johann Hofmann
  Dale Harvey

UX Team: 
  Stephen Horlander
  Michelle Heubusch

QA 
  Brindusa Tpt
  Ovidiu Boca

Testing summary

Scope of Testing

In Scope

This part of Photon project will redesign all UI components the browser with the new Photon style. In the scope of current testing are following areas in regards to the new look:

• General browser Overview(Normal, Compact, Touch)
• Different themes with their font colors
• Title bar, Menu bar, Tab bar
• Url bar with all the buttons, Search bar
• Bookmarks toolbar
• New icons/images within Photon style
• Customization page
• Notification bars (Default, Warning, Stop)

Out of Scope

Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.

Requirements for testing

Environments

Testing will be performed on the following OSes:

• Windows 10
• Windows 10 with touch
• Windows 7
• Mac OS X 10.12
• Ubuntu 16.04

Channel dependent settings (configs) and environment setups

Nightly

text

Beta

text

Post Beta / Release

text

Test Strategy

Risk Assessment and Coverage

ID	Description / Threat Description	Covered by Test Objective	Magnitude	Probability	Priority	Impact Score
RAC-1	Risk description 1	TO-1	2-Moderate	1-Unlikely	3-High	6
RAC-2	Risk description 2	TO-1	3-High	3-Almost Certain	3-High	27
RAC-3	Risk description 3	TO-2	2-Moderate	2-Possible	3-High	12

Values:

• Magnitude: 1- Low , 2-Moderate, 3-High

• Probability: 1-Unlikely, 2-Possible, 3-Almost Certain

• Priority: 1 - Low, 2-Medium, 3-High

Impact Score Breakdown:

• An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
• An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
• An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.

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	RAC	Owners
1	Name of the feature or sub-function being tested	The objective the test is trying to demonstrate	The criteria that will be evaluated to demonstrate the test is successful	Manual/ Automation/ Regression/ Performance/ Usability/ Security/ Telemetry	RAC-1, RAC-2, RAC-3	Eng Team
2	Repeat for each feature/sub-function
3

Builds

This section should contain links for builds with the feature -

• Links for Nightly 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
Study documentation/specs received from developers
QA - Test plan creation
QA - Test cases/Env preparation
QA - Nightly Testing
QA - Beta 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 Release/Beta

References

• List and links for specs

 List and links for available specs - documents, user stories, specifications

• Meta bug

Testcases

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	Yes	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	No	Make sure link to support/help page exist and is easy reachable.
Support documents planned(written)	No	Make sure support documents are written and are correct.
Install/Upgrade
Feature upgrades/downgrades data as expected	No
Does sync work across upgrades	No
Requires install testing	No	separate feature/application installation needed (not only Firefox)
Affects first-run or onboarding	No	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	No	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	No
Network proxies/autoconfig	No
ESR behavior changes	No
Locked preferences	No
Data Monitoring
Temporary or permanent telemetry monitoring	No	List of error conditions to monitor
Telemetry correctness testing	No
Server integration testing	No
Offline and server failure testing	No
Load testing	No
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?	No
Comprehensive API testing	No
Permissions	No
Testing with existing/popular addons	No
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	No
Privilege escalation testing	No
Fuzzing	No
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.	No
Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS	No
Interaction of this feature with other browser features	No

Test suite

Full Test suite - Link to test rail - testcases should be added under Firefox Desktop project link
Smoke Test suite - Link with the tests - if available/needed.
Regression Test suite - Link with the tests - if available/needed.

Bug Work

Meta bug: 12345 - bug summary

Logged bugs ( blocking 12345 )

Full Query

ID	Priority	Component	Assigned to	Summary	Status	Target milestone
15069	P3	Networking	jefft	File type url not correctly parsed and created	VERIFIED	M13

1 Total; 0 Open (0%); 0 Resolved (0%); 1 Verified (100%);

Bug fix verification

Full Query

ID	Priority	Component	Assigned to	Summary	Status	Resolution	Target milestone
15069	P3	Networking	jefft	File type url not correctly parsed and created	VERIFIED	FIXED	M13

1 Total; 0 Open (0%); 0 Resolved (0%); 1 Verified (100%);

Sign off

Criteria

Checklist

• 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
  • Full Test suite, link to TestRail - Tests Runs and Results link
  • Daily Smoke, if needed/available
  • Regression Test suite, if needed/available

Merge to Beta 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
Test Cases Creation
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
Metrics/Telemetry
Basic/Core functionality Nightly testing
QA mid-Nightly Signoff		Email to be sent
QA Nightly - Full Testing
QA pre-Beta Signoff		Email to be sent
QA Beta - Full Testing
QA pre-Release Signoff		Email to be sent