1362916 - [BackgroundSync] Migrate existing BackgroundSync tests to web-platform-tests when support for online/offline control is available to tests

Status: NEW

(Core :: DOM: Service Workers, task, P5)

Description

[Andrew Sutherland [:asuth] (he/him)]

The BackgroundSync API's behavior is dependent on whether the browser is online/offline.  So to properly test the API, tests need to be able to cause the browser to go online/offline, or at least make the BackgroundSync API think this has occurred.

This is a known limitation of the web-platform-tests at this time.  The general problem is tracked in https://github.com/w3c/web-platform-tests/issues/5669 with some related discussion on the (closed) https://github.com/w3c/web-platform-tests/issues/5558 and the public-test-infra thread with current most recent message at https://lists.w3.org/Archives/Public/public-test-infra/2017AprJun/0013.html.

This bug is to track moving to using web-platform-tests for as many things as possible.  (Especially for e10s glass-box testing, it could make sense to maintain a number of browser chrome tests.)

Comment 1

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Reading the comments, this issue depends on wpt framework support, seems not doable at this moment. So marking P3 now. Feel free to revise the priority as you see fit, Andrew! :)

Comment 2

[Jens Stutte [:jstutte]]

:asuth, is comment 1 still true?

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

I believe the WPT framework now has the infrastructure in place to support online/offline per https://web-platform-tests.org/writing-tests/testdriver-extension-tutorial.html, although no one has implemented online/offline.

That said, at this time we have no intent to ship backgroundsync and haven't landed the implementation we have, so there's no immediate action to take at this time.