QA/SHA384 Support

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
7/20/2017	1.0	Abe Masresha	Created first draft
8/10/2017	1.1	Abe Masresha	updated some sections
8/14/2017	1.2	Abe Masresha	updated some sections

Overview

Purpose

The purpose of this work is about adding support for stronger hash algorithms than SHA1. In this work support for SHA384 with a key size of 4096 bits will be applied.

Scope

• Testing will focus on:

Stability of the browser with this work.

Whether browser update is applied or not

If SHA384 support is applied to update

If SHA384 support has key size of 4096 bits

• How testing will be performed:

Manual

Ownership

Mozilla Development

 Robert Strong 

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, and Linux operating systems.

Out of Scope

Mobile devices are not affected by this work so this testing does not include them
Automation is handled by the developer

tests

tests

tests

Additional tests

Additional tests

Risk Analysis

• Update may not be applied so that the user may not get browser updates
• May behave differently in different operating systems
• Update may not be applied successfully if the browser has add-on
• May behave differently if update download is interrupted by no internet connection
• SHA384 support may not be applied
• SHA384 may not have key size of 4096 bits

Requirements for testing

Environments

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

Channel dependent settings (configs) and environment setups

Nightly

Firefox Nightly 56.0a1, no special configuration is required
This patch was pushed to Mozilla-central on 7-31-2017, so all Nightly updates should update through this watershed.

Beta

Beta 56.0b3, no special configuration is required
Feature was backed out Bug 1387231 so the watershed for beta will be 56b3.
To test on 56b3, 56b4 is required as this is update related work.

Test Strategy

Test Objectives

• Verify update is applied successfully
• Verify update is applied when the browser has an addon
• Verify browser is stable and does not crash with this feature
• Verify browser does not crash while updating
• Verify Firefox is responsive if update download is interrupted by no internet connection
• Verify SHA384 support is applied. More information is available here
  
• verify SHA384 has a key size of 4096 bits. More information is available here
  

Builds

This section should contain links for builds with the feature -

• Links for Nightly build: use the latest official Nightly build
• Links for Beta build: use the latest official beta build

Test Execution Schedule

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

Project phase	Start Date	End Date
Start project	5/30/2017
Study documentation/specs received from developers	7/20/2017	8/14/2017
QA - Test plan creation	7/20/2017	8/14/2017
QA - Test cases/Env preparation	7/20/2017	8/1/2017
QA - Nightly Testing	8/1/2017	8/1/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	TestRail / Google docs
Test case execution	TestRail
Bugs management	Bugzilla

Status

Overview

Landed on Nightly on: 7/31/2017
Merged to Beta on: [date]

References

• Main bug:1105689
  
• Meta bug:1324498

Testcases

Test Areas

Test Areas	Covered	Details
Private Window	Yes
Multi-Process Enabled	Yes
Multi-process Disabled	Yes
Theme (high contrast)	Yes
Install/Upgrade
Feature upgrades /Browser update	Yes	Will be covered on browser updates
Add-ons
Addon API required?	Yes
Testing with existing/popular addons	Yes	Feature functionality will be tested with popular addons
Web Compatibility
Survey of popular sites for compatibility	Yes	Firefox will be tested for stability with popular sites
Interoperability
Interaction of this feature with other browser features	Yes	Feature will be tested for its interaction with other browser features

Test suite

Full Test suite - Link to test rail - testcases 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

Bug No	Summary	Status	Firefox Version
			56
			56

Sign off

Criteria

Checklist

• 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: see 'Environments' section

• Link for the tests run
  • Full Test suite
    
  • Tests Runs and Results
    
  • Daily Smoke, if needed/available
  • Regression Test suite, if needed/available

Merge to Beta 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)	[DONE]
Testing Infrastructure setup	[DONE]
Test Plan Creation	[DONE]
Test Cases Creation	[DONE]
Automation Coverage		Covered by developer
Performance Testing		Covered by developer
All Defects Logged
Critical/Blockers Fixed and Verified
Basic/Core functionality Nightly testing
QA mid-Nightly Signoff		Missed (test build was not ready)
QA pre-Beta Signoff		Email to be sent
QA Beta - Full Testing
QA pre-Release Signoff		Email to be sent