MozillaWiki

QA/IntersectionObserver: Difference between revisions

< QA
(Initial template)
 
 
(38 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''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.
{| class="wikitable" style="width:60%"
|-
! Date !! Version !! Author !! Description
|-
| 11/23/2015 || 1.0 || Brindusa Tot || Created first draft
|-
| 10/05/2016|| 1.1 || Adrian Florinescu ||  Added point : 3.2 Channel dependent settings (configs) and environment setup
|}
= Overview =
= Overview =
== Purpose ==
== Purpose ==
Detail the purpose of this document. For example:
This wiki details the testing that will be performed by QA for the Intersection Observer API. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:
* The test scope, focus areas and objectives
* Areas of risk
* 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 <project name> project. 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
* What will be tested
* How testing will be performed
* How testing will be performed
** criteria
** ownership
** schedule
To help ensure the best possible release and long term maintenance of this feature.


== Ownership ==
== Risk Analysis ==
What resources are needed, and when (developers, QA, PMs working on the feature)
{| class="wikitable" style="width:95%"
= Testing summary =
== Scope of Testing ==
=== In Scope ===
Detail what is in scope from a testing perspective for the project team.
 
=== Out of Scope ===
Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.
 
= Requirements for testing =
== Environments ==
Specify OSes that need to be covered
Specify Devices that need to be covered
Specify other configuration/environmental setup needed
 
 
== Channel dependent settings (configs) and environment setups ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
 
=== Nightly ===
<div class="mw-collapsible-content">
text
</div>
 
=== Aurora ===
<div class="mw-collapsible-content">
text
</div>
 
=== Beta ===
<div class="mw-collapsible-content">
text
</div>
 
=== Post Beta / Release ===
<div class="mw-collapsible-content">
text
</div>
</div>
 
= 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.
 
{| class="wikitable"
|-
|-
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners
! Risk area !! Requirement !! Status
|-
|-
| 1 || Name of the feature or sub-function being tested || The objective the test is trying to demonstrate || The criteria that will be evaluated to demonstrate the test is successful || Manual/ Automation/ Regression/ Performance/ Usability/ Security/ Telemetry || Eng Team
| Ad intensive web pages || No regression in interaction performance || style="background-color:#CCFF99;" | PASS on Nightly 54
|-
|-
| 2 || Repeat for each feature/sub-function || || || ||
| Security || Fuzz testing finds no security holes || style="background-color:#CCFF99;" | PASS on Nightly 54
|-
|-
| 3 || || || || ||
| Stability || Crash rate does not increase || style="background-color:#CEF2F2;" | TBD
|}
|}


 
= Testing Strategy =
== Builds ==
== Scope ==
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.
{| class="wikitable" style="width:60%"
|-
! Project phase !! Start Date !! End Date
|-
| Start project
|style="text-align:center;" |  ||
|-
| Study documentation/specs received from developers
|style="text-align:center;" |  ||
|-
| QA - Test plan creation
|style="text-align:center;" |  ||
|-
| QA - Test cases/Env preparation
|style="text-align:center;" |  ||
|-
| QA - Nightly Testing  
|style="text-align:center;" |  ||
|-
| QA - Aurora Testing
|style="text-align:center;" |  || 
|-
| QA - Beta Testing
|style="text-align:center;" |  ||
|-
| Release Date
|style="text-align:center;" | ||
|}
 
== Testing Tools ==
Detail the tools to be used for testing, for example see the following table:
{| class="wikitable" style="width:50%"
|-
! Process !! Tool
|-
| Test plan creation || Mozilla wiki
|-
| Test case creation || [https://testrail.stage.mozaws.net/index.php TestRail]/ Google docs
|-
| Test case execution || [https://testrail.stage.mozaws.net/index.php TestRail]
|-
| 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
  List and links for available specs - documents, user stories, specifications
* Meta bug
= Testcases =
== Overview ==
Summary of testing scenarios
 
== Test Areas ==
{| class="wikitable" style="width:80%"
{| class="wikitable" style="width:80%"
|-
|-
! Test Areas !! Covered !! Details
! Test Areas !! Covered  
|-
|-
| Private Window  
| Private Window  
|style="text-align:center;" | ||
|style="text-align:center;" | Yes
|-
|-
| Multi-Process Enabled  
| Multi-Process Enabled  
|style="text-align:center;" |  ||
|style="text-align:center;" |  Yes
|-
|-
| Multi-process Disabled  
| Multi-process Disabled  
|style="text-align:center;" |  ||
|style="text-align:center;" |  Yes
|-
|-
| Theme (high contrast)
| Stability
|style="text-align:center;" | ||
|style="text-align:center;" | Yes
|-
|-
| '''UI'''  
| '''UI'''  
||  ||
||   
|-
| Mouse-only operation 
|style="text-align:center;" |  ||
|-
| Keyboard-only operation 
|style="text-align:center;" |  ||
|-
|-
| Display (HiDPI)  
| Display (HiDPI)  
|style="text-align:center;" | ||
|style="text-align:center;" | Yes
|-
|-
| Interraction (scroll, zoom)  
| Interraction (scroll, zoom)  
|style="text-align:center;" | ||
|style="text-align:center;" | Yes
|-
| Usable with a screen reader 
|style="text-align:center;" |  || e.g. with NVDA
|-
| Usability and/or discoverability testing 
|style="text-align:center;" |  || Is this feature user friendly
|-
| RTL build testing 
|style="text-align:center;" |  ||
|-
| '''Help/Support'''
||  ||
|-
| Help/support interface required 
|style="text-align:center;" |  || Make sure link to support/help page exist and is easy reachable.
|-
| Support documents planned(written) 
|style="text-align:center;" |  || Make sure support documents are written and are correct.
 
|-
| '''Install/Upgrade'''
||  ||
|-
| Feature upgrades/downgrades data as expected 
|style="text-align:center;" |  ||
|-
| Does sync work across upgrades 
|style="text-align:center;" |  ||
|-
| Requires install testing   
|style="text-align:center;" |  || separate feature/application installation needed (not only Firefox)
|-
| Affects first-run or onboarding   
|style="text-align:center;" |  || 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 
|style="text-align:center;" |  || 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 
|style="text-align:center;" |  ||
|-
| Network proxies/autoconfig 
|style="text-align:center;" |  ||
|-
| ESR behavior changes 
|style="text-align:center;" |  ||
|-
| Locked preferences 
|style="text-align:center;" |  ||
 
|-
| ''' Data Monitoring '''
||  ||
|-
| Temporary or permanent telemetry monitoring 
|style="text-align:center;" |  || List of error conditions to monitor
|-
| Telemetry correctness testing 
|style="text-align:center;" |  ||
|-
| Server integration testing 
|style="text-align:center;" |  ||
|-
| Offline and server failure testing 
|style="text-align:center;" |  ||
|-
| Load testing 
|style="text-align:center;" |  ||


|-
|-
| ''' Add-ons '''  
| ''' 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? 
| ad-blocking Add-ons must be disabled/removed to test
|style="text-align:center;" |  ||
|style="text-align:center;" |  Yes
|-
| Comprehensive API testing 
|style="text-align:center;" |  ||
|-
| Permissions 
|style="text-align:center;" |  ||
|-
| Testing with existing/popular addons
|style="text-align:center;" |  ||


|-
|-
| ''' Security '''  
| ''' 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 
|style="text-align:center;" |  ||
|-
| Privilege escalation testing
|style="text-align:center;" |  ||
|-
|-
| Fuzzing   
| Fuzzing   
|style="text-align:center;" |  ||
|style="text-align:center;" |  Yes
 
|-
|-
| ''' Web Compatibility '''  
| ''' Web Compatibility '''  
||  || depends on the feature
||   
|-
|-
| Testing against target sites   
| Testing against target sites   
|style="text-align:center;" |  ||  
|style="text-align:center;" |  Yes
|}
 
If it's not listed above, it is currently out of scope.
 
== Objectives ==
{| class="wikitable" style="width:95%"
|-
|-
| Survey of many sites for compatibility 
! Criteria Description
|style="text-align:center;" |  ||
! Metric
 
! w/o IO API
! w/ IO API
! Criteria Met?
! QA Owner
|-
|-
| ''' Interoperability  '''
| Manual testing
|| || depends on the feature
| Interaction performance
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Yes on Nightly 54
| Tracy 
|-
|-
| Common protocol/data format with other software: specification available. Interop testing with other common clients or servers. 
| Unit testing
|style="text-align:center;" | ||  
| Automated tests
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Yes on Nightly builds of 54
| Tobias
|-
|-
| Coordinated testing/interop across the Firefoxes: Desktop, Android, iOS 
| Fuzz testing
|style="text-align:center;" | ||  
| Automated tests
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Pass [1]
| style="background-color:#CCFF99;" | Yes on Nightly 54
| Fuzzing team (Raymond)
|-
|-
| Interaction of this feature with other browser features 
| Stability
|style="text-align:center;" | ||  
| Telemetry/Crash reports
| tbd - telemetry experiment in [https://bugzilla.mozilla.org/show_bug.cgi?id=1341259 bug 1341259]
| tbd - telemetry experiment in [https://bugzilla.mozilla.org/show_bug.cgi?id=1341259 bug 1341259]
| style="background-color:#CEF2F2;" | soon to begin with 10% enabled
| Tobias
|}
|}
[1] [https://bugzilla.mozilla.org/show_bug.cgi?id=1343807 tracking bug] has no bugs hanging off of it


== Test suite ==
== Testcases ==
Full Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1N8dGK_uenhfcM9cEPC3HPHmi0jFN98FWtL2DuszrfLY/edit#gid=0 link]
Ad-hoc testing of Ad-intensive websites. In general news sites tent to be rich of Ads. Therefore the top news sites on Alexa are a great source for suitable websites.
Smoke Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1N8dGK_uenhfcM9cEPC3HPHmi0jFN98FWtL2DuszrfLY/edit#gid=0 link]
Regression Test suite - Link with the gdoc - if available/needed.


= Bug Work =
[http://www.alexa.com/topsites/category/Top/News] The top 500 news sites on the web
Tracking bug – meta bug


<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
List of known sites using the Intersection Observer API:


====== Bug fix verification ======
* https://soundcloud.com/charts/top
<div class="mw-collapsible-content">
* http://news.yahoo.co.jp
{| class="wikitable" style="width:50%"
* http://www.iza.ne.jp/kiji/entertainments/newslist/entertainments-n1.html
|-
* http://www.bbc.com/sport/all-sports
! Bug No !! Summary !! Status !! Firefox Verion
* http://money.cnn.com/video/media/2016/10/13/rogue-one-trailer-good-morning-america.cnnmoney?iid=EL
|-
* http://money.cnn.com/2016/11/25/media/rogue-one-tickets/
|  123 || bug summary || NEW || Nighly 45
* http://abc7news.com/pets/hillsborough-mountain-lion-goes-viral/1658809/
|-
| || || ||
|}
</div></div>


<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
Possible test scenarios:


====== Logged bugs ======
* Open a single news site. Wait till it is fully loaded to make sure all Ads are properly initialized. If there is content to scroll, scroll up and down a couple of times. Click on some articles to trigger a refresh.
<div class="mw-collapsible-content">
Bug 111111<br/>
Bug 211111<br/>
</div>
</div>


* Open a multiple news sites in different tabs. Wait till every page is fully loaded to make sure all Ads are properly initialized. Switch between tabs from time too time. Close and open new tabs randomly. If there is content to scroll, scroll up and down a couple of times. Click on some articles to trigger a refresh.


= Sign off =
* Repeat scenarios above but let the browser untouched for a longer period of time. Then proceed.
== 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 ==
== Environments ==
'''Nightly testing'''<br />
Full Testing will be performed using Nightly for Desktop builds on:
* Windows
* Mac OS X
* Linux


List of OSes that will be covered by testing<br />
Full Testing will be performed using Nightly for Mobile builds on:
*Link for the tests run
* Android
** Daily Smoke, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Full Test suite, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Regression Test suite, if needed/available


'''Merge to Aurora Sign-off'''
== Channel dependent settings (configs) and environment setups ==
List of OSes that will be covered by testing<br />
* In Nightly  (and DevEd when available)- dom.IntersectionObserver.enabled needs to be set to "true" in about:config
*Link for the tests run
*If any kind of Ad-blocker is installed/in use it needs to be uninstalled/disabled
** Full Test suite


== Checklist ==
== Manual Testing Results ==
Ad-hoc testing around testcases and scenarios above in regular and private windows, in e10s and non-e10s windows and on normal and HiDPi displays.
=== Nightly ===
{| class="wikitable" style="width:60%"
{| class="wikitable" style="width:60%"
|-
|-
! Exit Criteria !! Status !! Notes/Details
! Platform
! IO disabled
! IO enabled
! QA'd by : build ID
|-
|-
| Testing Prerequisites (specs, use cases)
| Windows
| style="text-align:center;" |  
| style="background-color:#CCFF99;" | Pass
| style="text-align:center;" |  
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Tracy : 20170228030203
|-
|-
| Testing Infrastructure setup
| Mac
|style="text-align:center;" |   ||  
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Tracy : 20170228030203
|-
|-
| Test Plan Creation
| Linux
| style="text-align:center;" |   ||  
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Tracy : 20170301110155
|-
|-
| Test Cases Creation
| Android
|style="text-align:center;" |   ||  
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Pass
| style="background-color:#CCFF99;" | Tracy : 20170301110150
|}
 
=== Aurora ===
{| class="wikitable" style="width:60%"
|-
|-
|  Full Functional Tests Execution
! Platform
|style="text-align:center;" | 
! IO disabled
|style="text-align:center;" | 
! IO enabled
! QA'd by : build ID
|-
|-
| Automation Coverage ||
| Windows
|style="text-align:center;" |  
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|-
|-
| Performance Testing
| Mac
|style="text-align:center;" | ||  
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|-
|-
| All Defects Logged || ||  
| Linux
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|-
| Android
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|}
=== Beta ===
{| class="wikitable" style="width:60%"
|-
|-
|  Critical/Blockers Fixed and Verified || ||
! Platform
! IO disabled
! IO enabled
! QA'd by : build ID
|-
|-
| Metrics/Telemetry||  
| Windows
|style="text-align:center;" |  
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|-
|-
| QA Signoff  - Nightly Release||  
| Mac
|style="text-align:center;" | Email to be sent
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|-
|-
| QA Aurora - Full Testing
| Linux
|style="text-align:center;" | ||  
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|-
|-
| QA Signoff  - Aurora Release ||  
| Android
|style="text-align:center;"| Email to be sent
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | (results)
| style="background-color:#CEF2F2;" | TBD
|}
 
= Project Information =
== Ownership ==
Developer contacts: [mailto:tschneider@mozilla.com Tobias Schneider] <br />
QA: [mailto:twalker@mozilla.com Tracy Walker] <br />
QA Peer: <span style=color:red> TBD </span>
 
== Builds ==
This section should contain links for builds with the feature
* [https://nightly.mozilla.org/ Links for Nightly builds]
 
== Schedule ==
The following table identifies the anticipated testing period available for test execution.
{| class="wikitable" style="width:60%"
|-
|-
|  QA Beta - Full Testing
! Project phase !! Start Date !! End Date
|style="text-align:center;" |  ||
|-
|-
|  QA Signoff  - Beta Release ||  
| Start project
|style="text-align:center;" | Email to be sent
|style="text-align:center;" | 20160128 ||    tbd
|-
| Study documentation/specs received from developers
|style="text-align:center;" | 20170201 ||    20170210
|-
| QA - Test plan creation
|style="text-align:center;" | 20170210 ||    20170215
|-
| QA - Nightly Testing
|style="text-align:center;" | 20170227 ||    20170301
|-
| Telemetry - Stability Experiment
|style="text-align:center;" | 20170304?? ||    tbd
|-
| QA - Aurora Testing
|style="text-align:center;" | tbd ||   
|-
| QA - Beta Testing
|style="text-align:center;" | tbd ||  
|-
| Release Date
|style="text-align:center;" | tbd ||
|}
|}
== References ==
* List and links for specs
** [https://wicg.github.io/IntersectionObserver/] Intersection Observer Spec
** [https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API] Intersection Observer API
 
* Meta bug
** [https://bugzilla.mozilla.org/show_bug.cgi?id=1321865 Bug 1321865] - Enable IntersectionObserver

Latest revision as of 17:46, 3 March 2017

Overview

Purpose

This wiki details the testing that will be performed by QA for the Intersection Observer API. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:

  • Areas of risk
  • What will be tested
  • How testing will be performed
    • criteria
    • ownership
    • schedule

To help ensure the best possible release and long term maintenance of this feature.

Risk Analysis

Risk area Requirement Status
Ad intensive web pages No regression in interaction performance PASS on Nightly 54
Security Fuzz testing finds no security holes PASS on Nightly 54
Stability Crash rate does not increase TBD

Testing Strategy

Scope

Test Areas Covered
Private Window Yes
Multi-Process Enabled Yes
Multi-process Disabled Yes
Stability Yes
UI
Display (HiDPI) Yes
Interraction (scroll, zoom) Yes
Add-ons
ad-blocking Add-ons must be disabled/removed to test Yes
Security
Fuzzing Yes
Web Compatibility
Testing against target sites Yes

If it's not listed above, it is currently out of scope.

Objectives

Criteria Description Metric w/o IO API w/ IO API Criteria Met? QA Owner
Manual testing Interaction performance Pass Pass Yes on Nightly 54 Tracy
Unit testing Automated tests Pass Pass Yes on Nightly builds of 54 Tobias
Fuzz testing Automated tests Pass Pass [1] Yes on Nightly 54 Fuzzing team (Raymond)
Stability Telemetry/Crash reports tbd - telemetry experiment in bug 1341259 tbd - telemetry experiment in bug 1341259 soon to begin with 10% enabled Tobias 
[1] tracking bug has no bugs hanging off of it

Testcases

Ad-hoc testing of Ad-intensive websites. In general news sites tent to be rich of Ads. Therefore the top news sites on Alexa are a great source for suitable websites.

[1] The top 500 news sites on the web

List of known sites using the Intersection Observer API:

Possible test scenarios:

  • Open a single news site. Wait till it is fully loaded to make sure all Ads are properly initialized. If there is content to scroll, scroll up and down a couple of times. Click on some articles to trigger a refresh.
  • Open a multiple news sites in different tabs. Wait till every page is fully loaded to make sure all Ads are properly initialized. Switch between tabs from time too time. Close and open new tabs randomly. If there is content to scroll, scroll up and down a couple of times. Click on some articles to trigger a refresh.
  • Repeat scenarios above but let the browser untouched for a longer period of time. Then proceed.

Environments

Full Testing will be performed using Nightly for Desktop builds on:

  • Windows
  • Mac OS X
  • Linux

Full Testing will be performed using Nightly for Mobile builds on:

  • Android

Channel dependent settings (configs) and environment setups

  • In Nightly (and DevEd when available)- dom.IntersectionObserver.enabled needs to be set to "true" in about:config
  • If any kind of Ad-blocker is installed/in use it needs to be uninstalled/disabled

Manual Testing Results

Ad-hoc testing around testcases and scenarios above in regular and private windows, in e10s and non-e10s windows and on normal and HiDPi displays.

Nightly

Platform IO disabled IO enabled QA'd by : build ID
Windows Pass Pass Tracy : 20170228030203
Mac Pass Pass Tracy : 20170228030203
Linux Pass Pass Tracy : 20170301110155
Android Pass Pass Tracy : 20170301110150

Aurora

Platform IO disabled IO enabled QA'd by : build ID
Windows (results) (results) TBD
Mac (results) (results) TBD
Linux (results) (results) TBD
Android (results) (results) TBD

Beta

Platform IO disabled IO enabled QA'd by : build ID
Windows (results) (results) TBD
Mac (results) (results) TBD
Linux (results) (results) TBD
Android (results) (results) TBD

Project Information

Ownership

Developer contacts: Tobias Schneider
QA: Tracy Walker
QA Peer: TBD

Builds

This section should contain links for builds with the feature

Schedule

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

Project phase Start Date End Date
Start project 20160128 tbd
Study documentation/specs received from developers 20170201 20170210
QA - Test plan creation 20170210 20170215
QA - Nightly Testing 20170227 20170301
Telemetry - Stability Experiment 20170304?? tbd
QA - Aurora Testing tbd
QA - Beta Testing tbd
Release Date tbd

References

  • List and links for specs
    • [2] Intersection Observer Spec
    • [3] Intersection Observer API
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/IntersectionObserver&oldid=1164524"