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
03/30/2017	1.0	Ciprian Georgiu	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 Net Monitor MVP 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

What resources are needed, and when (developers, QA, PMs working on the feature)

Engineering contact(s):

• Jan Honza Odvarko (:Honza)

QA contact(s):

• Florin Mezei (:FlorinMezei) - Project Manager of the Release QA Team
• Andrei Vaida (:avaida) - Team lead of Release QA Team
• Ciprian Georgiu (:ciprian_georgiu) - leading QA efforts
• Iulia Cristescu (:IuliaC) - leading QA efforts (peer)

Testing summary

Scope of Testing

In Scope

Testing efforts will be focused on confirming that Net Monitor MVP is working as expected across platforms.

Out of Scope

Only the Net Monitor MVP feature functionality will be included in the testing efforts. Any others functionalities, that are not related to this feature, are not going to be evaluated in order to find whether it satisfies the specified requirements or not.

Requirements for testing

Environments

Full testing will be done on following OSes:

• Windows 7
• Windwos 10
• Ubuntu 16.04 LTS
• Ubuntu 14.04 LTS
• Mac OS X 10.11 or greater

About Netmonitor MVP

The Network Monitor shows you all the network requests Firefox makes (for example, when it loads a page, or due to XMLHttpRequests), how long each request takes, and details of each request. The Network Monitor records network requests any time the Toolbox is open, even if the Network Monitor itself is not selected. This means you can start debugging a page in, for example, the Web Console, then switch to the Network Monitor to see network activity without having to reload the page.

In product development, the minimum viable product (MVP) is a product with just enough features to gather validated learning about the product and its continued development.

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	Netmonitor Details panel (Header) is working properly	The Headers tab is properly displayed and lists the basic info about the request: request URL request method remote IP address and port status code the HTTP request and response headers that were sent a button to edit and resend the request	all scenarios provided must have the right expected result	Manual	Desktop Team
2	Netmonitor Details panel (Cookies)	The Cookies tab correctly lists full details of any cookies sent with the request or response.	all scenarios provided must have the right expected result	Manual	Desktop Team
3	Netmonitor Details panel (Params)	The Params tab is properly displays the GET parameters and POST data of a request.	all scenarios provided must have the right expected result	Manual	Desktop Team
4	Netmonitor Details panel (Response)	The Response tab is properly displayed and if the response is HTML, JS, or CSS, it will be shown as text. If the response is JSON, it will be shown as an inspectable object. If the response is an image, the tab displays a preview.	all scenarios provided must have the right expected result	Manual	Desktop Team
5	Netmonitor Details panel (Timings)	The Timings tab is displayed properly with the following subset of the stages defined in the HTTP Archive specification: Blocked DNS resolution Connecting Sending Waiting Receiving.	all scenarios provided must have the right expected result	Manual	Desktop Team
6	Netmonitor Details panel (Security)	The Security tab is properly displayed with details about the secure connection used including the protocol, the cipher suite, and certificate details.	all scenarios provided must have the right expected result	Manual	Desktop Team

Builds

This section should contain links for builds with the feature -

• Links for Nightly builds
• 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	17-03-2017	tbd
Study documentation/specs received from developers	17-03-2017	17-03-2017
QA - Test plan creation	31-03-2017	31-03-2017
QA - Test cases/Env preparation	17-03-2017	17-03-2017
QA - Nightly Testing	n/a	n/a
QA - Aurora Testing	20-03-2017	21-03-2017
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	[1]/ Google docs [2]
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 Aurora
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: [3].

Testcases

Test Areas

Test Areas	Covered	Details
Private Window
Multi-Process Enabled
Multi-process Disabled
Theme (high contrast)
UI
Mouse-only operation
Keyboard-only operation
Display (HiDPI)
Interaction (scroll, zoom)
Usable with a screen reader		e.g. with NVDA
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		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		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		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 to test rail - tascases 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: - (netmonitor-html) [meta Migrate Net panel to HTML]

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

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
Test Cases Creation
Full Functional Tests Execution
Automation Coverage
Performance Testing
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