use device-out-of-range.js bluetooth layout test to test other characteristic methods |
|||||
Issue descriptionthird_party/WebKit/LayoutTests/bluetooth/script-tests/characteristic/device-out-of-range.js can be modified to test other characteristic methods.
,
Jan 31 2017
It would be nice if these things were shared. Maybe we can address this when we move to web platform tests?
,
Jan 31 2017
,
Feb 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 21 2018
+odejesush@ since they've been working on the WPT migration.
,
Feb 22 2018
I can definitely add more characteristic methods, then convert and migrate the service-is-removed.js tests. The device-out-of-range.js might require the scanning API to be implement, or it could be simulated with a method like setNextGATTConnectionResponse/setNextGATTDiscoveryResponse. I'll have to ask Giovanni about that. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dougt@chromium.org
, Dec 7 2016