TEST INSTITUTE / how we test
How we test
Useful tests start with an honest question: what can this browser actually tell us?
Observe first. Explain second.
A camera preview confirms that your browser receives video. A key lighting up confirms that a keyboard event reached this page. Those are useful observations. Neither is a certificate that the hardware is fault-free.
We put the test first, explain the method underneath, and make the next troubleshooting step easy to find. A limitation is part of the result.
Three kinds of results
Browser-reported settings. Camera dimensions, frame-rate settings, and microphone sample rate come from the active stream. They describe what the browser reports, not a laboratory measurement.
Observed input. Microphone levels, key presses, pointer positions, and button events show what reaches this page. Operating-system settings and browser behavior affect them.
Your observation. Headphone channel checks and screen patterns need you to listen or look. We label your confirmations rather than deciding for you.
Designed to stay local
These six tests run on your device. Camera video, microphone samples, keyboard events, and pointer inputs are not uploaded. There are no advertising scripts, analytics beacons, or user accounts in this version.
When a test cannot run
Permission denied, unsupported features, and missing hardware get a specific message wherever the browser exposes that distinction. A page cannot override an operating-system restriction. Try the suggested checks and compare with another app before concluding that hardware is faulty.
What we don’t claim
Test Institute is a browser utility collection, not an accredited laboratory. These tools do not diagnose hearing, eyesight, or health; certify equipment; or measure calibrated acoustic or display performance.