Open Quake now has an opt-in acceptance suite that runs its desktop software against a real keyboard using the project's firmware. The first live run passed 13 of 20 scenarios, a useful result because the project records the seven gaps instead of letting mocked human interface device (HID) tests stand in for hardware evidence.
The suite checks the exact device identity before opening it, takes an ownership lock, exercises control readback and keepalive behavior, and restores reversible settings during cleanup. It writes diagnostics and the tested revision to an atomic result file, so an interrupted run can't leave behind a report that looks complete. A separate supervised check asks for fresh confirmation, types one a through the production keyboard path, observes the key release, and then verifies cleanup.
The suite draws a practical boundary between unattended tests and physical acceptance. The software can automate transport, state restoration, and evidence capture, while a person still confirms the action that could affect the host computer. Embedded teams building desktop tools should start with that split and publish the scenario count; a partial 13-of-20 result is more actionable than a green mock suite with no record of what happened on the device.