How We Test: Our Capability & Evidence Standards

A web browser is not a native hardware engineering lab. It operates inside a secure sandbox with restricted permissions. To maintain absolute technical honesty, every tool on ElixerPro.tools displays an explicit Capability Badge classifying its exact evidence tier.

Tier A — Direct Browser Interaction

Tier A

The browser directly accesses hardware events through official W3C Web APIs and displays user-observable interactions.

Examples: Keyboard key event detection, Dead Pixel solid color cycling, Webcam local preview, Microphone waveform meter, Gamepad stick input.
Evidence Level: High. Directly verifies whether peripheral signals reach the operating system and browser.

Tier B — Browser Estimate

Tier B

Calculated approximations derived from timing loops, rendering callbacks, or hardware concurrency hints.

Examples: Screen refresh rate (sampled via requestAnimationFrame), CPU benchmark calculations, Mouse event frequency (Hz), Network latency round-trip time.
Evidence Level: Statistical estimate. Accurately labeled with sample sizes, variance histograms, and environmental caveats.

Tier C — Guided System Check

Tier C

Hardware properties that web browsers are strictly prohibited from reading due to sandboxing and security policies.

Examples: Battery cycle capacity, CPU silicon temperature, physical fan RPM, SSD SMART health, motherboard USB port inventory.
Evidence Level: Guided native workflow. We provide step-by-step verified operating system instructions (PowerShell, macOS System Info, Linux terminal, BIOS) to check hardware safely without risky third-party downloads.

Tier D — Companion-App Territory

Tier D

Advanced component repairs, circuit probing, or oscilloscope-level hardware diagnostics that cannot exist in a web browser.

Our Approach: We clearly explain the architectural barrier and refer readers to certified technician diagnostic tools rather than building fake web simulations.

Result Classification

Every test result on ElixerPro.tools uses honest, specific wording:

Looks good: The tested interaction behaved as expected under the specific parameters of this test.
Check this: An anomalous reading was observed, but cannot conclusively diagnose the root cause.
Issue observed: A repeatable test interaction failed to register under valid test conditions.
Unable to test: The current browser or operating system did not expose the required API, or permission was denied.

Have questions or suggestions about our testing standards?

Read our Editorial Policy or email our technical review team at moqeems209@gmail.com.