W3C home > Mailing lists > Public > public-device-apis-log@w3.org > September 2018

Re: [sensors] Introduce WebDriver extension API

From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Sep 2018 13:28:07 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-420647723-1536758886-sysbot+gh@w3.org>
I don't have access to the slides you linked to, but looking at testdriver's code again I think we're both right: when one runs wptrunner the code in testdriver-extra.js (which uses WebDriver) is used; when the tests are run in Chromium's CI and `run_web_tests.py` (or rather just not via wptrunner) testdriver-vendor.js is used instead (and there's no WebDriver involved). I had the latter case in mind, but forgot about the former.

Now going back to my original question: how do you see this spec in terms of API? Would we e.g. switch from `let sensorTest = await initialize_generic_sensor_tests()` in `generic-sensor/generic-sensor-tests.js`'s `sensor_test()` to something that tells WebDriver to start mocking one or more sensor types, or is there something else besides that?

GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/sensors/pull/369#issuecomment-420647723 using your GitHub account
Received on Wednesday, 12 September 2018 13:28:13 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:55 UTC