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
13/07/2016	1.0	Ciprian Muresan & Vlad Bacia	Created first draft
06/10/2016	1.1	Bogdan Maris	Updated testplan
24/07/2017	1.2	Ciprian Georgiu	Updated testplan

Overview

Purpose

The Simplify Page feature is a printing option that enables the user to print articles through the Reader View feature, in essence simplifying the page and changing the fonts for it to be more legible.

Scope

This wiki details the testing that will be performed for the Simplify Page feature. It defines the overall testing requirements and provides an integrated view of the project test activities.

Ownership

Engineering - Matheus Longaray
Platform Engineer - Mike Conley (irc: mconley)

QA:

• Nightly:

PM for QA team - Rares Bologa (irc: RaresB)
Leading QA efforts - Paul Oiegas (irc: pauloiegasSV)
QA - Ciprian Muresan (irc: cmuresan)

• Dev Edition, Beta, Release:

QA Lead: Bogdan Maris mail , :bogdan_maris on IRC

Feature email address: TBD

Testing summary

Scope of Testing

In Scope

The goal is to use Reader View when printing pages.

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:

- Mac OS X testing
- 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 14.04
• Ubuntu 16.04

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	Simplify Page is on	Verify that the “print.use_simplify_page” is set to true in about:config	Observe the pref value	Manual	Eng Team
2	Simplify Page functionality	Verify that the feature works	1. Print Preview an article 2. Click the Simplify Page checkbox	Manual	Eng Team
3	Private Browsing	Verify that the feature works while in private browsing	1. Print Preview an article 2. Click the Simplify Page checkbox	Manual	Eng Team
4	Availability	Verify the availability of the option	1. Pages which have Reader View available can be simplify-able 2. Pages which don’t have Reader View available can’t be simplify-able	Manual	Eng Team
5	Simplify Page is off	Set “print.use_simplify_page” to false	The simplify page checkbox no longer appears in Print Preview	Manual	Eng Team

Builds

This section should contain links for builds with the feature -

• Link for Nightly builds
• Links for Developer Edition 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	01/03/2016	- 21/07/2017
Study documentation/specs received	05/07/2016	06/07/2016
QA - Test plan creation	13/07/2016	14/07/2016
QA - Test cases/Env preparation	14/07/2016	15/07/2016
QA - Nightly Testing	22/05/2017	02/06/2017
QA - Beta Testing	17/07/2017	21/07/2017
Release Date	-	-

Testing Tools

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
  
• 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 the Print feature	Simplify Page is dependent on the ability to print https://bugzilla.mozilla.org/show_bug.cgi?id=1285547

References

• Use Reader Mode for printing articles
• Enable Simplify Print Feature by default

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	No
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	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
Feature upgrades/downgrades data as expected	N/A
Does sync work across upgrades	No	Not relevant
Requires install testing	No
Affects first-run or onboarding	No
Does this affect partner builds? Partner build testing	No	We won't have partner builds available for testing in the Nightly or Aurora channels
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	No
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?
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	Yes
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 - Google doc with test cases
• Smoke Test suite -
• Regression Test suite -

Bug Work

 Meta bug - Use Reader Mode for printing articles

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

• Link for the tests run
  • Daily Smoke suite -
  • Full Test suite -
  • Regression Test suite, if needed/available

Merge to Aurora Sign-off

• Link for the tests run -
  • Full Test suite -

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	[DONE]
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
Daily Status Report (email/etherpad statuses/ gdoc with results)
Metrics/Telemetry		N/A
QA pre-Beta signoff - Testing in Nightly		[DONE] 02/06/2017
Testing in Beta		[DONE] 10/07/2017 to 21/07/2017
QA pre-Release Signoff - Testing in Beta		[DONE] 21/07/2017