The DualSense is not a standard gamepad with a PlayStation logo on it. It carries a touchpad, adaptive triggers with real mechanical resistance, a six-axis motion sensor, a microphone, a speaker, and dual HD haptic actuators, on top of the buttons and sticks every controller has. A tester built for a generic XInput pad can confirm the basics and miss every one of those, which is exactly why a dedicated PS5 controller tester covers more ground and why reading its results takes a bit more context than a standard rumble-and-stick check.
Here's what each part of the test actually checks, what a healthy result looks like, and what a failure in each specific area usually means.
Buttons, d-pad and sticks
The baseline check is the same as any controller: every face button, bumper, and d-pad direction should register exactly once per press, and both sticks should read dead centre at rest with your thumbs off them.
The DualSense's sticks use conventional potentiometers, the same wear-prone mechanism found in nearly every mainstream controller, which means they're genuinely susceptible to drift over time rather than being an exception. If a stick's resting value sits off centre, that's drift, not a connection issue, and the size of the offset tells you how far along the wear actually is. Our dedicated PS5 drift test guide goes through reading that number specifically and what threshold is worth acting on versus just compensating with a small deadzone.
L3 and R3, the stick clicks, are tested separately from stick movement itself, since they're a distinct physical switch beneath the stick module. A stick that moves and reads correctly but doesn't register a click, or clicks on its own under light pressure, is a separate fault from drift even though both live in the same component.
Adaptive triggers
This is the feature a generic tester has no way to check at all. The DualSense's L2 and R2 triggers contain a small motor and gear mechanism that can physically resist your pull, not just vibrate, creating tension that a game can vary in real time, like the increasing resistance of drawing a bowstring.
A proper test checks two separate things here. First, the basic analog range: trigger value should read 0 at rest and climb smoothly to 100 at full pull with no dead spot or early clipping, same as any analog trigger on any controller. Second, and unique to this hardware, whether the resistance motor itself engages and releases correctly when commanded, since a trigger can report perfect analog values while its resistance motor has failed entirely, a combination that feels wrong in-game even though the numbers look fine. If one trigger offers no resistance at all while the other works, or if you hear grinding or clicking from inside the housing during a resistance test, that is a mechanical fault specific to that trigger module. Our guide on adaptive triggers not working covers that failure pattern in detail, including the cases that are a software setting rather than a hardware fault.
Touchpad
The touchpad is tested for both click registration and touch tracking, which are two different physical layers. The click is a single button beneath the entire pad surface, essentially one large button rather than many separate zones, so a click that registers in the centre but not near the edges points at an uneven mechanical press rather than a dead switch, since it's the same switch either way.
Touch tracking is separate: moving a finger across the pad should produce smooth, continuous coordinate values, not jumps or dead zones partway across the surface. Intermittent tracking that comes and goes, especially with light dust or moisture on the pad, is extremely common and usually solved by cleaning before you assume a fault. Persistent dead zones that clean up every time are more likely a genuine sensor fault under that section of the pad. Our full breakdown of touchpad troubleshooting separates the cleaning fixes from the cases actually worth a repair or replacement.
Motion sensors
The DualSense's six-axis IMU is genuinely one of the better sensors in a mainstream controller, low noise and stable, and testing it is the same process as any gyro-equipped pad: rest the controller on a flat surface, hands off, and confirm pitch, yaw and roll all sit close to zero and stay there. A small steady offset on one axis is ordinary sensor bias and clears up with recalibration. Values that wander or jump erratically point at something more serious, though this is a comparatively rare failure on DualSense hardware specifically.
Vibration and haptics
The DualSense uses HD dual actuators rather than the simpler eccentric-mass motors found in older pads, built to reproduce texture and sharp transients rather than generic buzz. A full test fires each actuator independently and at varying intensity, since a motor that works at full strength but produces nothing at low intensity has a real fault that a simple on/off check would miss entirely. Our guide on testing PS5 controller vibration specifically covers reading that result against what's normal for this particular hardware, since HD actuators behave differently from the ERM motors most troubleshooting advice online was written around.
Worth remembering separately: PS5 controls overall haptic intensity at the system level, under Settings, then Accessories, then Controllers, independently of any single game or test page. A DualSense that feels weak across every test is worth checking there before assuming a motor has failed.
Battery and charging
Not every tester checks this, but it matters for a wireless controller specifically. A DualSense that connects and inputs correctly over USB but won't pair or stay connected over Bluetooth is frequently a battery health issue rather than a radio fault, since a degraded battery can hold enough charge to power basic functions wired while failing to sustain a wireless radio link. If charging itself is the problem, whether that's a controller that won't charge at all or one that shows a concerning light pattern while plugged in, our guide on PS5 controller charging issues covers the full set of causes from cable faults to a genuinely degraded internal battery.
Testing a DualSense Edge
The Edge adds swappable stick modules, two sets of back paddle buttons, and onboard profile switching, and each of these deserves its own check rather than assuming they inherit the standard DualSense's behaviour. Back buttons are wired as fully separate inputs from the face buttons they're typically mapped to, so a profile that doesn't fire correctly might be a mapping issue in the Edge's own software rather than a dead button. The swappable stick modules mean a drift problem can sometimes be solved by swapping to a spare module entirely rather than troubleshooting the stick in place, which is a genuinely different repair path from a standard DualSense where the sticks are fixed in the shell.
Wired versus wireless, and what changes
Testing over USB removes Bluetooth as a variable entirely, which makes it the right first step whenever a result looks ambiguous. If a fault appears wired, it's the controller. If a fault only appears wireless, test Bluetooth connection quality and battery health before concluding anything about the controller's physical components, since a weak wireless link can produce symptoms, like dropped inputs or muted haptics, that look identical to a hardware fault but clear up completely over a cable.
Microphone and speaker
Two features most testers skip entirely, partly because browser access to them is more restricted than access to buttons and sticks, and partly because they're genuinely secondary to how the controller plays. The built-in microphone is mono and intended for quick voice chat without a headset, not a replacement for one, so a muffled or quiet result against a dedicated headset isn't a fault, that's the hardware's actual ceiling. The speaker handles specific in-game sound cues in supporting titles, like a radio crackle or an environmental effect, rather than general game audio, so testing it against expectations for full game sound will always disappoint regardless of whether it's working correctly.
Common false positives worth ruling out first
A few results look like a hardware fault but usually aren't. A stick that reads slightly off centre immediately after unboxing a brand new controller is more often a factory calibration variance than drift, and it's worth running the test again after the controller has been used normally for a day or two before concluding anything, since true wear-based drift develops gradually rather than appearing instantly on a fresh unit. A controller that behaves differently in a browser test than in a specific game is more often that game's own deadzone or sensitivity curve than a hardware issue, since the test and the game are reading the same raw signal but interpreting it differently. And a fault that appears only in one specific browser, but not another, points at that browser's Gamepad API implementation rather than the controller, since the hardware itself has no awareness of which browser is reading it.
How this compares to testing other controllers
Running a DualSense through its dedicated tester versus running a standard Xbox pad through a generic one highlights how much extra ground this specific hardware covers. An Xbox controller's test is comparatively short: buttons, sticks, triggers, two rumble motors, done. The DualSense's extra layers, the touchpad, the adaptive trigger motors, the dual HD actuators, the motion sensor, the microphone and speaker, mean there's genuinely more that can go wrong, but also genuinely more information available when something does, which is a fair trade for a controller with this much hardware packed into it.
Reading an overall result
A controller that passes every section cleanly, on both USB and Bluetooth, with sticks centred, triggers resisting correctly, touchpad tracking smoothly, and every haptic motor firing at every tested intensity, is genuinely healthy and any remaining in-game complaint is worth looking at in game or platform settings rather than the hardware itself. A controller that fails one isolated section while passing everything else almost always has a problem contained to that specific component, which is useful information whether you're deciding what to clean, what setting to check, or what to describe in a warranty claim.