QA/Client Crash Id

QA/Client Crash Id

Revision History

Date	Version	Author	Description
02/24/2017	1.0	Abe Masresha	Created first draft

Overview

Purpose

The goal of this feature is to align the breakpad-generated crash id with a crash report.

Scope

• Testing will focus on:

Functionality and stability of Crash Reporter Client.

Validating the crash report.

Validating the content crash ping.

Comparing browser crash pings from the minidump file and ping received after a restart.

Comparing content crash pings from the minidump file and ping received after a restart.

Stability of the browser with this work.

• How testing will be performed:

Manual

Risk analysis

This work includes modifications to both the crash reporter client and the code that handles content process crashes. So the risk will mainly base on those two:

• First, it may break the crash reporter client in a way that prevents the user from sending crash reports or causes submitted crash reports to be malformed
• Second, it may not send crash pings for the content crash, or send malformed crash pings.

Ownership

Mozilla Development

Gabriele Svelto

QA Eng. Softvision Las Vegas
Stefan Georgiev - Team Lead
Abe Masresha - Test Lead
Justin Williams - Tester
Grover Wimberly IV - Tester
Kanchan Kumari - Tester

Testing summary

Scope of Testing

In Scope

This feature will be tested manually on Windows, Mac, Linux operating system and Android devices.

Out of Scope

Automation will be handled by the developer (if needed)
iOS devices will not be tested

Requirements for testing

Environments: Operating Systems

Windows 10 64bits
Windows 7 32 bits
Ubuntu 16.04 32 and 64bits
MacOSX 10.12
Android devices

Firefox Channel and environment setups

Build

Firefox Nightly 54.0a1

Test Strategy

Test Objectives

Verify Firefox is stable with this feature
Verify SHA256 hashed minidump file and the crash ping after restart are identical.
Verify the hashed minidump file and the restart crash ping contain minidumpSha256Hash field in the payload element.
Verify the hashed minidump and restart ping have identical contents for the minidumpSha256Hash field
Verify the hashed minidump file and the restart crash ping contain minidumpSha256Hash field in the payload element for Content Process Crash.
Verify the hashed minidump and restart ping have identical contents for the minidumpSha256Hash field for Content Process Crash.
Verify Firefox restarts successfully after crash
Verify crash reporter client is responsive and functional after or before the first ping

Test Execution Schedule

Project phase	Start Date	End Date
Start project	02/24/2017	TBD
Study documentation/specs received from developers	02/24/2017	02/16/2017
QA - Test plan creation	02/27/2017	TBD
QA - Test cases/Env preparation	02/27/2017	TBD
QA - Nightly	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	TestRail/ Test Cases GDoc
Test case execution	Test Cases TestRail
Bugs management	Bugzilla

References

Test cases: TestRail or Test Cases GDoc

Bugs: Bug 1310703 and Bug 1336360

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Private Window	Yes	Few tests will be made on private window as well
Non e10s Window	Yes	Few tests will be made with non e10s window as well
Install/Upgrade
Feature upgrades/downgrades data as expected	Yes	Feature will be tested against browser updates
Data Monitoring
Temporary or permanent telemetry monitoring	Yes	Data from Local telemetry server will be monitored
Telemetry correctness testing	Yes	Data correctness will be tested.
Server integration testing	Yes	feature will send data to a telemetry server and this functionality will be tested
Offline and server failure testing	Yes	Server offline option will be included in testing
Add-ons
Testing with existing/popular add-ons	Yes	feature functionality will be tested with popular addons
Web Compatibility
Survey of popular sites for compatibility	Yes	Firefox will be tested for stability
Interoperability
Common protocol/data format with other software: specification available. Interop testing with other common clients or servers.	Yes	first and second ping data will be compared
Interaction of this feature with other browser features	Yes	Firefox will be tested for stability across popular sites.

Test suite

Full Test suite - [ Test Cases TestRail]/ Test Cases GDoc

Bug Work

Tracking bugs – bug

Bugs

Bug No	Summary	Status	Firefox Version
Bug 1341282	NEW	The telemetry session id field of the crash ping sent by the crashreporter client is wrong	54
			54

Sign off

Criteria

Check list

• All test cases should be executed
• All blocker and critical bugs must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/developer/QA)

Results

Feature testing

• Links for the tests run
  • Full Test suite: [ Test Cases runs TestRail]
  • Regression Test suite: [link] if needed/available

Checklist

Exit Criteria	Status	Notes/Details
Testing Prerequisites (specs, use cases)	[DONE]	Specs
Testing Infrastructure setup	[DONE]
Test Plan Creation	[DONE]
Test Cases Creation	[DONE]	Test Cases TestRail/ Test Cases GDoc
Full Functional Tests Execution
Automation Coverage		will covered by developer if needed
Performance Testing		will covered by developer if needed
Load Testing		will covered by developer if needed
All Defects Logged
Critical/Blockers Fixed and Verified
Metrics/Telemetry
QA Signoff - Nightly Release
QA Aurora - Full Testing
QA Signoff - Aurora Release
QA Beta - Full Testing
QA Signoff - Beta Release