Try that button on its own and watch both press and release. If it is a side control, check whether it triggers navigation. Use the mouse button test for the focused comparison.
Mouse test
Run the mouse test to check button events, wheel direction and pointer movement. Use the result to choose a focused check, not to declare the whole device healthy or faulty from one short sample.
Also known as: mouse test, mouse tester, mice testing, mouse checker. Free, online, and no download required.
No permission neededNothing uploaded
Click, scroll or move the mouse inside the instrument to begin.
01
What the mouse test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Button response | Button indexes 0 through 4 have a pressed highlight and a count of recorded press cycles completed by a release. | A pressed button never produces a complete pair. |
| Wheel direction | Wheel events are counted by delta sign and retain their browser delta mode. | A requested direction is absent; unequal totals need a controlled repeat. |
| Duplicate clicks | Intervals below 40 ms on the same button are isolated as suspect duplicates. | A physical press repeatedly produces a second immediate event. |
How to run the mouse test
- Prepare the device and close any application that could reserve the same input or media stream.
- Start the mouse test, follow the live prompt and complete every named control or direction.
- Finish the run, record the verdict and repeat once before changing one setting or connection.
If something failed
Use a steady single-press rhythm and compare the same selected button in the double click test. Record repeated short intervals without assuming that one flagged pair identifies switch wear.
Keep each scroll movement in one direction and pause before reversing. Use the mouse scroll test to compare the event sequence with what your hand did, then try a second application.
Choose a focused check by symptom
| Symptom | Next test | Observe |
|---|---|---|
| Missing press or release | Mouse button test | Which button event is absent |
| One press produces two actions | Double click test | Repeated short intervals for the same button |
| Wheel jumps backwards | Mouse scroll test | Direction changes during one-way motion |
02
How to read the result
How the mouse test works
Test one action. This mouse tester groups several browser observations on the same page: button presses, releases, wheel events and pointer movement. Begin with the action that fails in ordinary use and describe what you expected to see, so that a complete counter for another control does not distract from the actual symptom.
Button indexes represent actions exposed to the browser. Press the primary, secondary and wheel buttons separately, releasing each fully before the next press. Side buttons may be used for navigation or remapped elsewhere. If an action is missing here, compare its assigned function before deciding that the control itself failed.
Does the pointer move smoothly while a button is held? Test dragging separately from simple movement, because a lost press can interrupt a drag even when the pointer continues across the stage. Keep the cursor inside the instrument while comparing runs and reset the counters before trying another device.
Choose the next mouse check
A silent button belongs in the mouse button test, where press and release observations remain the focus. A repeated single click belongs in the double click test. The symptom should select the next page; opening every instrument does not make an incomplete observation more useful.
Does the wheel reverse while your hand keeps turning it in one direction? Use the mouse scroll test and separate upward and downward movements with a pause. Unequal totals alone are not a diagnosis, since the distance and speed of your two movements may differ.
For a broken pointer path, compare another surface and the same movement in another application. If the complaint is the frequency of movement updates rather than missing buttons, continue with the mouse polling rate test. Keep its result separate from click-to-paint timing.
What the result can establish
Mouse test results describe the events received during the sample, not the raw USB reports. It does not prove that the device will behave the same way in a game, another application or a later session. Note the affected control and the observed action, then repeat that action under the same conditions before changing a setting.
The duplicate counter flags intervals below 40 ms on the same button as suspect. That is the site's review threshold, not a measurement of the switch mechanism. Deliberate fast presses can enter the same region. A repeated pattern gives you a reason to collect a focused sample, not a confirmed explanation of its cause.
Wheel direction comes from event deltas rather than how far the page moves. Free-spin wheels and trackpads can produce different sequences from notched wheels. Read the mode and the actions you performed together; do not compare two different input methods as if they delivered identical physical steps.
Measurement limits
The mouse checker cannot inspect electrical contacts, sensor firmware or physical travel. Browser and operating-system processing affect the sequence received by the stage. A trail gap can reflect a delivery or drawing interruption, so its appearance alone does not identify a failed sensor.
Keep a comparison record. Include the button or movement, the connection, the application and the result after one change. The how to test a mouse guide explains how to compare those observations without treating a different port or browser as proof that every other cause has been removed.
03
Mouse test questions
Is this mouse tester free, and does it need a download?
Yes. The mouse test runs in this browser tab without installing a driver or creating an account. Place the pointer inside the stage and use a control to begin. It records the events delivered to the page; it does not connect to a service that can inspect or repair the mouse hardware.
Which controls does the mouse button test actually cover?
The page separates the button actions the browser exposes, including primary, secondary, wheel and side controls where available. A remapped button can behave differently from its physical location. If a side press navigates the browser instead, compare that assignment in another application before treating an unlit entry as a fault.
Why does the mouse scroll test show uneven wheel counts?
The totals describe received wheel events, not matching physical distances. Your upward and downward movements may differ, and notched wheels, free-spin wheels and trackpads can use different delta modes. Repeat with separate one-way movements. An uneven count by itself does not establish skipped encoder steps or a repair requirement.
Which focused mouse test should I run next?
Choose the mouse button test for missing presses or releases, the double click test for repeated single clicks, and the mouse scroll test for reverse jumps. For pointer movement, compare the same surface and application first. Each focused tool should answer the particular question left unresolved by the general run.
How should I repeat the mouse test fairly?
Reset before each comparison and repeat the same controls with the same mouse, connection and browser. Keep the sample focused on the original symptom. Change one setting or connection after recording the first result, then repeat the sequence so you can describe what changed without mixing counts from two setups.
What can the mouse test not prove?
It cannot establish physical switch wear, sensor accuracy or firmware health. It also cannot inspect another application's input processing. A completed sample describes the events received here. Use a repeatable symptom and a comparison in the affected application when choosing the next test or describing the issue to support.