Record the question you are testing
A useful test begins with a specific behavior: one key appears to repeat after a single press, a game chord loses an input or a release seems absent. Choose a short routine that is easy to repeat and keep unrelated typing out of the capture area. The lab records only while its focused live session is running.
The synthetic example demonstrates the report format and includes deliberately constructed events. It is labeled as synthetic in both the interface and exported data. Always start a fresh live test before collecting your own evidence. A generated example, automated test or browser event sequence is not an independent physical inspection of your keyboard.
Read the summary together with the raw events
The summary separates distinct codes, automatic repeats, peak observed held keys and rapid repress candidates. Open the event list when a number looks surprising. A single candidate can have several explanations, especially when you intentionally tap quickly or move focus while a key remains held.
The JSON download retains configuration and the end reason with the observations. The CSV offers a straightforward sequence of relative time, event type, physical code and auto-repeat flag. No typed-character strings or raw device identifiers are included. Code sequences still describe your test activity, so review the file before sharing it publicly.
Compare carefully and clear local work
Use a previous report as a baseline only when the source type and rapid-repeat window match. Repeat the same pressing routine after a change and keep the session lengths similar. Different counts across unrelated routines do not establish improvement or deterioration. The comparison is an organizational aid, not a statistical diagnosis.
There is no account, automatic upload or persistent project storage in this lab. Download files you want to keep, then press Clear to remove the current session and baseline from memory or leave the page. Explain the browser and connection conditions separately when contacting support. The report documents what reached the browser; further device-specific troubleshooting may still be needed.