QA/Content Handling

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/24/2016	1.0	William Hsu	Initial 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 Content Handler 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

• EPM (Manager: Vance Chen)

• Wesly Huang

• UX (Manager: Harly Hsu)

• Bryant Mao
• Carol Huang - Visual Designer
• Morpheus Chen

• Front End (Manager Evelyn Hung)

• Sean Lee
• YiFan Liao

• Platform (Manager: Ben Tian)

• Alphan Chen
• Eden Chuang
• Will Wang

• QA (Manager: Al Tsai)

• William Hsu

Testing summary

Scope of Testing

In Scope

In this project, we intend to improve the content handling experience of Firefox Desktop. The enhancement includes scenarios such as “open with” dialog), a file is saved (download panel), the way dealing with that file (content handling, in pref. → App.), and relevant platform side design refactoring. Therefore, the testing effort for Content Handling will be invested on the following areas:

1. Release Acceptance testing
2. Compatibility testing - Backward compatibility
3. Continuous integration
4. Destructive testing (Forced-Error Test)
5. Functional vs non-functional (Scalability or other performance) testing
6. Performance testing
7. Regression testing
8. Usability testing

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.

1. Accessibility testing (UX will deal with it)
2. L10N test (L10n team will deal with it)
3. Scan security hole (Security team will deal with it. If any patches exist security concern, we will add "sec-review" flag on the bug)

Requirements for testing

Environments (TBC)

• Linux
• Linux x64
• OS X 10.7
• OS X 10.10
• Windows XP
• Windows 7
• Windows 8 x64

Test Strategy

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	File handler	Verify download process	1. Pop out download starting notification when a new download request is triggered. 2. There is no Opening dialog.	Manual	Eng Team
2	Download panel	Verify the number of maximum download items displayed	Max numbers of download items displayed at the same time: 5	Manual	Eng Team
3	Download panel - Summary section	Verify the summary section for Multiple Files information in Downloads Panel	1. New Icon in summary section 2. Format change of downloading/completeness status 3. ETA format is changed to Xm XXs left 4. Show the overall network speed. [1] https://mozilla.invisionapp.com/share/4Y6ZZH1E8#/screens/156737043	Manual	Eng 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	03/28/2016	TBD
Study documentation/specs received from developers	05/20/2016	05/27/2016
QA - Test plan creation	05/24/2016	05/27/2016
QA - Test cases/Env preparation	05/20/2016	05/27/2016
QA - Nightly Testing	TBD	TBD
QA - Aurora Testing	TBD	TBD
QA - Beta Testing	TBD	TBD
Release Date	TBD	TBD

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

Identify the high-risk assumptions
Identify existing bugs on the feature with high risk
Identify if other areas are affected by the fix

References

• List and links for specs

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

• Meta bug

Testcases

Overview

Summary of testing scenarios

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)
Interraction (scroll, zoom)
Usable with a screen reader		e.g. with NVDA
Usability and/or discoverability testing		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
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 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

Bug fix verification

Bug No	Summary	Status	Firefox Verion
123	bug summary	NEW	Nighly 45

Logged bugs

Bug 111111
Bug 211111

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, 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
Test Cases Creation
Full Functional Tests Execution
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