How to test your mouse
- Choose the device you are actually using. Keep a trackpad test separate from a mouse test.
- Put the pointer in the test area and press each available button once. Try the wheel as a button as well as a scroll control.
- Choose “Hold, move, release” and the button you want to check. Hold the primary, secondary or middle button for at least 2 seconds and move inside the area. Wait for “You can release”, then release that same button. Short holds, absent movement and interruptions remain separate observations.
- Compare the wheel’s directions, then observe one direction for 5 seconds. Choose your wheel type and axis, start the observation and scroll steadily in one direction inside the area. The first event on your chosen axis starts the timer. Move outside the area to scroll the page normally; this interrupts an active observation.
- Review the observations. Download a local report if you want to compare another connection or application.
What the results mean
Detected means the browser received a press for that logical button. It does not certify the physical switch. Not observed means no matching press reached this test; the button may be absent, reassigned, intercepted or simply untested.
Hold and move records pointer movement while at least one button is held. The last and longest completed holds use the browser’s event timestamps. A release is counted separately from a hold ended because you left the area or changed windows. It does not reveal whether a release was intentional, measure a sensor’s accuracy or prove that a long drag will never disconnect. Leaving the area or changing windows ends the current hold observation so the drawing cannot remain stuck.
The 5-second wheel observation separates brief reversals followed by a return, sustained direction changes, pauses and unconfirmed reversals. These are event patterns, not proof of a faulty wheel or your intended gesture. A free-spinning wheel or trackpad can continue sending momentum events. The report keeps the chosen axis and browser units separate and explains its observation windows; these have not been calibrated as hardware fault thresholds.
Wheel directions describe the sign of scroll changes received by this page. The value can be reported in pixels, lines or pages. One browser event is not one physical notch, and trackpad gestures can generate the same kind of event. System settings can reverse the relationship between your gesture and the reported direction.
Something looks wrong? Check this next
| Observation | Useful next check |
|---|---|
| A button stays unobserved | Check its assignment in your system or mouse software. Try the same action in another application and another browser. |
| Left and right appear swapped | Check the primary-button setting. This test labels logical actions, so a left-handed configuration can be working as intended. |
| A hold ends unexpectedly | Repeat entirely inside the test area without switching windows. If it also happens elsewhere, compare another port, connection or device. |
| One press seems to click twice | Use the double-click observation test with deliberate, spaced single presses. |
| Wheel input is missing or changes direction | Check scroll settings, then compare another application. A trackpad’s momentum and gestures can produce additional scroll events. |
Compatibility and limits
This tool needs a browser that exposes Pointer Events and wheel events. Touches and pen input are identified separately and do not increase the mouse-button counter. A trackpad may report itself as a mouse; the device selector records your stated test context, not automatic hardware identification.
Extra buttons are shown only when the browser exposes their logical signals. Some buttons run a system shortcut or navigate away before the page can observe them. The test handles context menus only inside its area; your browser’s commands remain available elsewhere.
These observations cannot certify a model, polling rate, latency or electrical fault. Read our testing method and validation limits before treating a result as a hardware conclusion.
Do clicks leave my device?
The test processes button and scroll observations in this page’s memory. It does not upload your input, store a movement history or identify your device. Resetting or leaving clears the observations. Your report appears below the test as observations become available. “Download PDF” creates a file on your device with your chosen setup, button, guided observations and method limits, without a print dialog or an external conversion service. TinyFingers uses its existing Google Analytics for general page and tool usage; input details are not sent. About TinyFingers and privacy.