How we test and write

The guides and test pages are written by the DeviceKite editorial team. This page explains how.

Tests

Every calculation has automated tests with known answers: a full-scale sine wave must read −3.01 dBFS and a full-scale square wave 0.00 dBFS; 47 clicks in 5 seconds must give 9.40 clicks per second; a ruler caught after 20 cm must give 202 ms (t = √(2d/g), g = 9.81 m/s²); 300 characters typed in a minute with 10 uncorrected errors must give 60 gross and 50 net words per minute. The full list is kept with the source code.

The tests are tried in Chrome, Safari and Firefox on desktop and phone. Where a browser lacks a feature (for example choosing a speaker output or reading a raw mouse polling rate), the page says so instead of guessing.

Guides

Troubleshooting steps follow the help pages of the operating-system, browser and app makers. Each guide lists its sources and the date the steps were last checked. Menus change with updates, so if a step no longer matches what you see, please tell us.

No invented numbers

We do not publish “average” scores that we cannot source. Fun tiers on the skill tests are labelled as our own. Where we quote a published figure, we cite it.

Corrections

Write to contact@devicekite.com. We fix errors quickly and update the date on the page.