[w3c/gamepad] Interop 2025 investigation effort - Gamepad API testing (Issue #219)

nondebug created an issue (w3c/gamepad#219)

See also: #175

As part of Interop 2025, we are running an Investigation Effort to improve testability of the Gamepad API.

https://github.com/web-platform-tests/interop/blob/main/2025/README.md#gamepad-api-testing

Gamepad API currently lacks WPT test coverage for most of the API surface. Automated tests only cover feature policy, not-fully-active state, and IDL.

https://github.com/web-platform-tests/wpt/blob/master/gamepad/feature-policy-gamepad.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/gamepad-default-feature-policy.https.sub.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/gamepad-supported-by-feature-policy.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/not-fully-active.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/idlharness.window.js

There are a handful of manual tests that require the tester to connect a gamepad:

https://github.com/web-platform-tests/wpt/blob/master/gamepad/events-manual.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/gamepad-dual-rumble-effect-manual.https.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/gamepad-trigger-rumble-effect-manual.https.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/getgamepads-polling-manual.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/idlharness-manual.html
https://github.com/web-platform-tests/wpt/blob/master/gamepad/timestamp-manual.html

The goal of this effort is to expand test coverage to include automated tests that exercise parts of the API that rely on simulating device behaviors (connection, disconnection, button/axis/touchpad state change, vibration).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/219
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/219@github.com>