QA/Pointer events: Difference between revisions
Line 226: | Line 226: | ||
== Checklist == | == Checklist == | ||
<TBD> |
Revision as of 13:42, 21 September 2016
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 |
---|---|---|---|
09/19/2016 | 1.0 | Alexandru Simonca | 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 Pointer Events project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document what and how we shall test:
- Permissions are listed and correctly managed for devices using this feature
- Events are recorded in the DevTools Console
- Website compatibility issues
Ownership
Development
Developer: Stone Shih (irc:stone)
QA:
Alexandru Simonca - Leading QA Efforts
Iulia Cristescu - QA Peer Review
Testing Summary
Scope of Testing
In Scope
Testing efforts will currently be focused on ensuring that the expected PointerEvents are triggered by the expected initiators, on various websites compatible with this feature.
Out of Scope
<TBD>
Requirements for testing
Environments
In terms of platform coverage, testing will focus on Windows-only, starting with (and including) Windows 7.
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.
- Permissions are listed and correctly managed
- Events are recorded in the DevTools Console
- Website compatibility
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 | 09/19/2016 | TBD |
Study documentation/specs received from developers | 09/19/2016 | TBD |
QA - Test plan creation | TBD | TBD |
QA - Test cases/Env preparation | TBD | TBD |
QA - Nightly Testing | TBD | TBD |
QA - Aurora Testing | TBD | TBD |
QA - Beta Testing | TBD | TBD |
Release Date | 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 case execution | TestRail |
Bugs Management | Bugzilla |
Status
Overview
Track the date and build number when feature was merged to Nightly
Track the date and build number when feature was merged to Aurora
Track the date and build number when 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
- Meta bug: 822898 - Implement pointer events
Testcases
Test Areas
Test Suite
Full Test Suite - Link with tests in TestRail *link here when available*
Bug Work
Tracking Bug - meta Bug 822898 - Implement pointer events
Bug fix verification
Bug No | Summary | Status | Firefox Version |
---|---|---|---|
795567 | Implement touch-action CSS property for Pointer Events | Verified Fixed | Nighly 51 |
967796 | Implement Pointer Enter/Leave events support | Verified Fixed | Nighly 51 |
968148 | Implement PointerCapture for pointer events | Verified Fixed | Nighly 51 |
970964 | Implement generic mouse/touch -> Pointer events converter | Verified Fixed | Nighly 51 |
974305 | Needs a test for WidgetPointerEvent::AssignPointerEventData() if it's possible | Verified Fixed | Nighly 51 |
977695 | Update bubbles/cancelable attribute for pointer events | Verified Fixed | Nighly 51 |
979497 | Once DispatchPointerFromMouseOrTouch is called, aFrame can be deleted object (i.e. what should be target for the mouse events if a listener for pointer events modifies the DOM) | Verified Fixed | Nighly 51 |
985511 | When a pointing device that supports hover leaves the range of the digitizer while over an element, the pointerleave event must be dispatched | Verified Fixed | Nighly 51 |
987078 | If pointerType is "mouse" and buttons > 0, then pressure must be 0.5 | Verified Fixed | Nighly 51 |
996493 | Implement MaxTouchPoints for Windows widget | Verified Fixed | Nighly 51 |
1066237 | MaxTouchPoints variable may return invalid value on the win7 platform | Verified Fixed | Nighly 51 |
1122211 | Dispatch Pointer Events in Win32 (Windows desktop) widget code | Verified Fixed | Nighly 51 |
1137555 | [e10s] Navigator.maxTouchPoints doesn't work on e10s with dom.w3c_pointerevents.enabled = true and dom.w3c_touch_events.enabled=1 | Verified Fixed | Nighly 51 |
1149861 | Implement getMaxTouchPoints for Android | Verified Fixed | Nighly 51 |
1153130 | Firefox crashes when pointer events are enabled | Verified Fixed | Nighly 51 |
1153135 | When APZC is enabled FireFox cannot generate PEN events into content. | Verified Fixed | Nighly 51 |
1162009 | POINTER_CANCEL does not work in e10s | Verified Fixed | Nighly 51 |
Sign off
Criteria
- All test cases should be executed
- Has sufficient automated test coverage
- All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed
Results
Nightly Testing
- Link for the tests run
- Full Test suite, in TestRail at <insert TestRail link here when available>
- Regression Test suite, if needed/available
Merge to Aurora Sign-off
- Link for the tests run
- Full Test suite
Checklist
<TBD>