QA/Shield

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
5/12/2016	1.0	Adrian Florinescu	Created first draft
10/10/2016	1.1	Adrian Florinescu	Updates

Overview

Scope

This wiki details the testing that will be performed by the QA-Eng team for the SHIELD project. SHIELD is a system addon that addresses user attrition and satisfaction in Firefox. User facing products that are included in SHIELD and on which the current test plan will focus are:

• Shield Studies - Recruits users to participate in testing new features and ideas that help us validate product decisions.
• Heartbeat - Gathers feedback from users for us to better understand what users find helpful and useful
• Self Repair - Detects problems with Firefox and suggest fixes to the user
• Contextual Feature Recommendation - Allows users to discover features and addons based on how they use the product

One of the main focuses of the QA team will be the user facing products listed above, but QA focus shall be given to:

• SHIELD Recipe management
• SHIELD Control center
• Delivery system for the Shield recipes: how and if the filter expressions are targeting a certain niche of the FF users.

Ownership

Project Owner: Gregg Lind [:gregglind ]
Product Manager: Matt Grimes [:Matt_G]
Development: Michael Cooper [:mythmon]
Development: Michael Kelly [:Osmose]
Development: Gregg Lind [:gregglind]

PM, QA Engineeting Team - Rares Bologa
QA Engineering Team - Adrian Florinescu

Testing summary

Scope of Testing

In Scope

Detail what is in scope from a testing perspective for the project team.

Out of Scope

Out of the SHIELD two main components: Client Side and Server Side, the server side named Normandy does not fall under the scope of the current Test Plan.

Requirements for testing

Environments

TBD - Specify OSes that need to be covered Specify other configuration/environmental setup needed - The preliminary testing phase shall take place in Nightly 52, but the requirements for testing Shield as it graduates to system add-on will change. See Channel Configuration

Channel dependent settings (configs) and environment setups

Nightly

The initial tests that shall be conducted in the incipient testing phases will require a Normandy local setup (docker compose), Normandy-addon and several FF Client settings as follows. We expect these to be replaced by configurations that are delivered by Shield as a System Add-on.

1. Normandy - docker compose (for setting and configuring the environment see QAsetup)
   1. Hosts the control center
   2. Delivers recipes to target clients

1. FireFox Client
   1. Normandy add-on is required (the git for it is Git_normandy-addon ) which must be installed on the client FF
   2. Several preferences must also be set on the Client FF as follows where localhost must be replaced with the ip of the docker-compose Normandy:
      1. browser.selfsupport.url = "https://localhost:8443/%LOCALE%/repair"
      2. browser.uitour.testingOrigins = "https://localhost:8443"
      3. extensions.recipeclient.api_url = "https://localhost:8443/api/v1"
      4. security.content.signature.root_hash = "4C:35:B1:C3:E3:12:D9:55:E7:78:ED:D0:A7:E7:8A:38:83:04:EF:01:BF:FA:03:29:B2:46:9F:3C:C5:EC:36:04"

Aurora

text

Beta

text

Post Beta / Release

text

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	Control Center	Admin interface allows admin users to add/edit recipes	Basic configuration actions are possible	Manual/Usability	Eng Team
2	Recipe execution	Recipes created in the admin interface are delivered to the Client FF	The FF Client receives and executes the recipe	Manual	Eng Team
3	Peer approval	Recipes created in the admin interface need peer approval to be enabled	Each recipe created in the admin interface cannot be run without peer approval	Manual	Eng Team
4	Filter Expressions	Each recipe targets a particular bucket defined in filter expressions area in admin	Only FF matching the filter expressions will run the recipe	Manual	Eng Team
5	Sampling	Basic check on client running the recipe ratio	Heuristic approach to do a basic checking of the sampling set in the recipe	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	10.05.2016
Study documentation/specs received from developers	10.05.2016
QA - Test plan creation	12.05.2016
QA - Test cases/Env preparation	23.06.2016
QA - Nightly Testing
QA - Aurora 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	Test Rail
Test case execution	Test Rail
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
  • QAsetup
  • Normandy-addon
  • Shield Concepts

• Meta Bug 1275996 - [Tracker] SHIELD System Add-on v1.0

Testcases

Overview

Summary of testing scenarios - TBD

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 – Bug 1275996 - [Tracker] SHIELD System Add-on v1.0

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