Revision aaea1a41a04ac0ce565bbc59f296a647902de015 authored by Chandan Padhi on 08 March 2018, 11:46:05 UTC, committed by Blink WPT Bot on 08 March 2018, 15:58:25 UTC
InputDeviceInfo extends MediaDeviceInfo and represents audio and video input devices. These objects are the result of calling MediaDevices.enumerateDevices(). This interface gives access to the capabilities of the input device it represents via getCapabilities() method which will be implemented in asubsequent CL. Intent to implement and ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/h4sCuIqb_78 Bug: 817769 Change-Id: Ic9a016a05e622ee02b86d567f64c3ed84f0926c3 Reviewed-on: https://chromium-review.googlesource.com/942961 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#541772}
1 parent c36f238
README.md
# Web Bluetooth Testing
Web Bluetooth testing relies on the [Web Bluetooth Testing API] which must be
provided by browsers under test.
In this test suite `resources/bluetooth-helpers.js` detects and triggers
the API to be loaded as needed.
The Chromium implementation is provided by
`../resources/chromium/web-bluetooth-test.js`.
The Chromium implementation is not included in stable Chrome builds since it
would add too much to the binary size. On Chromium infrastructure, it is run
using the `content_shell` executable.
In the future, Chromium `src/device/bluetooth` may be refactored into a Mojo
service. At this point, it would be possible to add the necessary testing hooks
into stable Chrome without substantially increasing the binary size, similar to
WebUSB.
These bluetooth tests are upstreamed here because other browsers can reuse them
by implementing the [Web Bluetooth Testing API], even if only on their internal
infrastructure.
[Web Bluetooth Testing API]: https://docs.google.com/document/d/1Nhv_oVDCodd1pEH_jj9k8gF4rPGb_84VYaZ9IG8M_WY/
# Generated gen-* files from generator.py
`generator.py` builds `gen-*.html` tests using templates in
`script-tests/*/*.js`.
The subdirectory structure in `bluetooth/script-test/*` is recreated into
`bluetooth/*`. The generator expands each CALL function from templates
into new leaf directories and files.
Example:
`script-tests/server/get-same-object.js` contains:
```
gattServer.CALLS([
getPrimaryService('heart_rate')|
getPrimaryServices()|
getPrimaryServices('heart_rate')[UUID]]),
```
Generating:
```
server/getPrimaryService/gen-get-same-object.html
server/getPrimaryServices/gen-get-same-object.html
server/getPrimaryServices/gen-get-same-object-with-uuid.html
```
Usage:
```
$ python generate.py
```
More details documented in `generate.py`.
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...