QA/file read access

Overview

Purpose

This page details the testing that will be performed by QA file read access restrictions sand boxing functionality. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:

• Areas of risk
• What will be tested
• How testing will be performed
  • criteria
  • deliverables
  • ownership
  • schedule
• What data, if any, will be monitored

To help ensure the best possible release and long term maintenance of this feature.

Risk Analysis

Risk area	Requirement	Status
File Uploading	User has ability to upload files	TBD
Add-ons	File access properly restricted	TBD
about: pages	no regression in access of about: pages	TBD
3rd party hand-offs	TBD	TBD
Plugins (particularly Flash)	File access properly restricted	TBD
Profiles (user and Firefox) on "other" drives	File access properly restricted	TBD
Performance	No browser responsiveness regressions	TBD
Stability	No regressions in crash rate	TBD

Testing Strategy

Scope

Test Area	Covered	Notes
Multi-Process Enabled	Yes
Printing	Yes
Flash Plugin	Yes
Virtual Keyboard	Yes
Accessibility	Yes
Private Window	Yes
Install/Upgrade
Feature upgrades/downgrades data as expected	Yes
Does sync work	Yes
Enterprise		Profiles on network drives will be affected
Enterprise administration	Yes
Network proxies/autoconfig	Yes
ESR behavior changes	Yes
Data Monitoring
Temporary or permanent telemetry monitoring	Yes
Add-ons
Permissions	Yes
Testing with existing/popular addons	Yes
Web Compatibility		Focused on sites with file upload capability
Testing against target sites	Yes
Interoperability		Focus on third party hand-offs to/from Firefox
Common testing with other clients.	Yes

If it's not listed above, it is currently out of scope.

Objectives

Criteria Description	Metric	Test results	Criteria Met?	QA Owner
Manual testing	Tests passed	-link to manual test results-	TBD (Date status updated)	TBD
Unit testing	Automated tests pass	perfherder	TBD (Date status updated)	TBD
Security	Security approves via review	-Link to security Analysis-	TBD (Date status updated)	TBD
Stability	Crash rate stable	-link to Stability Analysis-	TBD (Date status updated)	TBD

Manual Testcases

• Focus should be on the following:
  • Printing
  • Print to file
  • file uploads to sites like google docs and photo sites
  • drag and drop of files into content
  • content file/page saves
  • add-ons:
    • WebExtensions
      • Popular WebExtensions still work
      • WebExtensions-developer use cases loading from home directory (i.e, about:debugging then load both packed and unpacked extensions)
    • Legacy
  • about:* pages are functional and links within access correctly
  • Flash (file picker)

Environments

Full Testing will be performed using Nightly for Desktop with focus one platform specific issues

• Windows
  • Accessibility (spot check NVDA)
  • Virtual keyboard support
  • Roaming windows user
  • Running from a network drive
  • Profile on network drive
  • Profile on symbolic link or junction point
  • Windows Users directory on junction point
    • especially printing with this
• Mac OS X
• Linux
  • Profile in symlinked dir
  • .config in symlinked dir
  • ~ (home) in symlinked dir
  • Various distros and desktop envs, Qt (with themes and GTK style engine) vs GTK
    • At the very least Fedora, Ubuntu and/or KDE or GNOME

Note: Read access restrictions on each platform will be slightly different. When creating test cases, any known differences should be called out in the test case.

Project Information

Ownership

Project Manager: Jim Mathies
Developer contacts: Bob Owen
QA: Tracy Walker
QA Peer: TBD (SV)

Builds

• Links for Nightly builds

Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase	Start Date	End Date
Start project	Q1/2016	Q2/2017
QA - Test plan creation	Q2/2017	Q2/2017
QA - Test cases/Env preparation	Q2/2017	Q2/2017
QA - Nightly Testing	Q2/2017	Q2/2017
QA - Beta Testing	Q2/2017	Q3/2017
Release Date	FF55	2017-08-08

References

• develepment bug: TBD