QA/Large-Allocation header
Large-Allocation header
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 |
|---|---|---|---|
| 2017-03-13 | 1.0 | Ciprian Georgiu | Created first 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 Large-Allocation header feature. 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
Engineering contact(s):
QA contact(s):
- Florin Mezei (:FlorinMezei) - Project Manager of the Release QA Team
- Andrei Vaida (:avaida) - Team lead of Release QA Team
- Ciprian Georgiu (:ciprian_georgiu) - leading QA efforts
Testing summary
Scope of Testing
In Scope
Testing efforts will be focused on confirming that browser (custom Firefox 53 build) works as expected when playing Facebook / other web games which take advantage of various web features when Large-Allocation header is present.
Out of Scope
Only the Large-Allocation feature behavior will be included in the testing efforts. Any others , are not going to be evaluated in order to find whether it satisfies the specified requirements or not.
Requirements for testing
Environments
Full testing will be done on following OSes:
- Windows 7 x86
- Windwos 10 x86
- Windwos 8.1 x86
About Large-Allocation header
The Large-Allocation response header tells the browser that the page being loaded is going to want to perform a large allocation. WebAssembly or asm.js applications can use large contiguous blocks of allocated memory. For complex games, for example, these allocations can be quite large, sometimes as large as 1GB. The Large-Allocation tells the browser that the web content in the to-be-loaded page is going to want to perform a large contiguous memory allocation and the browser can react to this header by starting a dedicated process for the to-be-loaded document, for example.
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.
Testing approach
- set up a smoke/acceptance suite that checks the core functionality associated to this feature, along with a few major UI components
- set up an exploratory section within this suite that checks all the UI components
Builds
This section should contain links for builds with the feature:
The feature is available on Firefox 53 starting with 2017-02-02.
- Links for Nightly builds - available since 02-02-2017 link
- Note that the special flag which turns it on for every website is only in the Firefox 53 custom build. [1]
| Ref | Function | Test Objective | Evaluation Criteria | Test Type | Owners |
|---|---|---|---|---|---|
| 1 | The custom Firefox 53 build works as expected when the LargeAllocation header is present on content loads |
|
all scenarios provided must have the right expected result | Manual | Desktop Team |