DESKPROOF / FIELD MAP
Which device test should I use?
Match the observation to the right instrument, then use a guide if the result needs explaining.
Choose by what you want to observe
| Instrument | Specific observation | Measurement limits |
|---|---|---|
| Keyboard tester | Observe physical-position key events and held combinations. | Browser key events, not electrical latency or every system shortcut. |
| Mouse test | Observe individual mouse buttons and their event counts. | Button input, not sensor DPI or an interval-based double-click diagnosis. |
| Double-click test | Compare deliberate single presses with received events and intervals. | Received press timing, not your physical intent or switch voltage. |
| Mouse wheel test | Observe wheel direction, horizontal deltas and their units. | Wheel deltas and units, not a physical notch or encoder inspection. |
| Gamepad tester | Inspect connected-controller buttons, triggers, mapping and live axes. | Live API input and mapping; a resting sample belongs in the drift tool. |
| Stick drift test | Take a five-second hands-off sample of radial stick offsets. | Radial browser offset, not a universal repair threshold or USB packet rate. |
| Dead pixel test | Inspect isolated fixed points across manually selected colors. | Your visual assessment of fixed points; no automatic defect detection. |
| Backlight bleed test for LCD monitors | Compare visible light patches on neutral backgrounds under recorded conditions. | Your visual comparison of light patches; no luminance sensor or panel diagnosis. |
A tool and its guide have different jobs
A test receives your input or shows a visual pattern. A guide explains a controlled comparison and what could affect it. A saved report records the observation; it does not establish the cause of a fault. Start with the tool, keep the conditions and consult the relevant guide when something unexpected repeats.