About
Browser tests for the hardware in front of you.
What this is
Pellick is a small set of tests that run in your browser and tell you whether a piece of your hardware is answering. The keyboard test is live, with its ghosting mode on a page of its own, and more tests are being built.
Each one is a single page. You arrive, you use it, you leave. Nothing to install and no step between the search result and the tool.
Why the tests say what they cannot do
Every test here carries a list of what it is unable to measure, with the technical reason beside it. That is unusual and it is deliberate.
A browser only ever knows what it received. When a key does not light up, the page knows the code did not arrive. It does not know whether the fault is the key, the cable, the firmware or the operating system, and saying otherwise would be inventing a verdict. The tests that are useful are the ones that separate what they know from what they are guessing, so that is the line this site draws in public.
How it is built
Static pages, no framework running in your browser, one downloaded font, and a measurement suite that exercises every test in Chromium, Firefox and WebKit before anything ships. What a page claims is checked against a document describing what its engine actually does, and the build fails when the two disagree.
What a browser cannot reach is tested by hand on real hardware, because an automated key press is not intercepted by an operating system the way a real one is, and a test suite that passes where a real machine would fail is worse than no suite.
Who
Pellick is built and run by one person. The contact page is the way to reach them: a correction, a browser that behaves differently from what a page claims, or a test worth building.