https://github.com/web-platform-tests/interop-gamepad
Gamepad API testing, part of Interop 2025
https://github.com/web-platform-tests/interop-gamepad
Last synced: 5 months ago
JSON representation
Gamepad API testing, part of Interop 2025
- Host: GitHub
- URL: https://github.com/web-platform-tests/interop-gamepad
- Owner: web-platform-tests
- Created: 2025-02-20T09:44:05.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-11-04T18:55:45.000Z (8 months ago)
- Last Synced: 2025-11-04T20:29:40.446Z (8 months ago)
- Language: HTML
- Size: 22.5 KB
- Stars: 1
- Watchers: 24
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Interop 2025: Gamepad API testing
Work on the [Gamepad API testing investigation effort](https://github.com/web-platform-tests/interop/blob/main/2025/README.md#gamepad-api-testing)
for [Interop 2025](https://github.com/web-platform-tests/interop/blob/main/2025/README.md).
## Why an investigation effort?
The goal of an interop focus area is to demonstrate improved interoperability by
increasing the pass rates of automated web platform tests on participating
browsers.
To qualify for an interop focus area, a feature needs good enough test coverage
to enable interoperability improvements to be scored using test results.
An [investigation effort](https://github.com/web-platform-tests/interop/blob/main/2025/README.md#investigation-efforts)
is a set of tasks that will bring the corresponding feature up to the bar that's
required for it to possibly become a focus area in the future.
For context, this investigation effort arose from a rejected
[focus area proposal](https://github.com/web-platform-tests/interop/issues/786).
This investigation effort is scoped to only the Gamepad API and is focused on
improving test coverage rather than fixing existing tests.
## Existing specifications
https://w3c.github.io/gamepad/
## Existing tests
https://github.com/web-platform-tests/wpt/tree/master/gamepad
## Known problems
Add a means to test the API [#175](https://github.com/w3c/gamepad/issues/175)
Most of Gamepad API cannot be tested by automated web platform tests.
The API does not expose any information about connected gamepads until a
[gamepad user gesture](https://w3c.github.io/gamepad/#dfn-gamepad-user-gesture)
is detected, and there is currently no way to simulate this gesture in tests.
Once the gesture is detected, tests also need a way to simulate other gamepad
interactions (connect, disconnect, buttons, axes, touch, vibration).
## Collaborators
| WebKit | Chromium | Gecko | Nvidia |
|-|-|-|-|
| @marcoscaceres | @nondebug | | @xingri |
## Progress status
* Review the current status of Gamepad tests on the web
* 100% complete
* Draft spec change to extend WebDriver BiDi for gamepad automation
* 100% complete
* [#224](https://github.com/w3c/gamepad/pull/224)
* Write manual interop tests
* 100% complete
* [Test suite](https://web-platform-tests.github.io/interop-gamepad/manual-tests.html)
* Conduct live interop testing and file bugs against the affected browsers
* 100% complete
* [Notes](https://docs.google.com/document/d/1oBV4K6rCZOn0p9XlMXBkLZBB-wcEPTUDtiCOwf_FusA/edit?tab=t.pqye8e4wjf1t#heading=h.pbf3d0wd6oz3)
* Implement gamepad automation API
* Chromium implementation
* 40% complete
* Safari implementation
* 0% complete
* Firefox implementation
* 0% complete
* Write web platform tests exercising gamepad behaviors
* 0% complete
## Notes
[Investigation of Gamepad Testing Model for Interop 2025](https://docs.google.com/document/d/1oBV4K6rCZOn0p9XlMXBkLZBB-wcEPTUDtiCOwf_FusA/edit?tab=t.0#heading=h.xarlmp6z56ks)