How we test

How we check every guide on a real device, which devices we use and how our tools work.

Last updated

Every guide on TweakSage is followed step by step on a real device before it goes up. This page explains how, on which devices, and what happens when something changes.

How we check a guide

  1. We follow each step on a real device running the system version the guide is for, and take our own screenshots along the way.
  2. We check every fact that does not come from our own testing against the maker’s documentation (Microsoft, Apple, Google, Samsung) and list those sources at the end of the guide.
  3. At the top of each guide you’ll see Steps checked on with the device, system version and date. If we could not test a step on a device ourselves, the guide says so.
  4. When Windows, iOS or Android change the steps, we check the guide again and note what changed under What changed in this guide.

Devices we test on

We currently test on an iPhone and a Windows laptop. Each guide names the exact model and system version in its Steps checked on note.

We don’t own every phone and computer. When a guide covers a device we don’t have, such as an Android phone or a Mac, those steps come from the maker’s own instructions, which we link under Sources, and the guide says that we could not check them ourselves.

How our tools work

  • Screen Test shows standard full-screen colours (for example pure white #FFFFFF), four gradients and a grid where every square is one device pixel.
  • Touch Screen Test splits your screen into squares of about 52 by 52 points and marks each one you touch, including fast swipes between two points.
  • What Phone Do I Have? reads the details your browser shares and compares iPhone screen sizes with Apple’s published specifications. Where a browser hides something, the tool says so instead of guessing.

All three run on your device. Nothing you test is sent to us.

Found a mistake?

Tell us through the contact page with your device and system version. We check it on a device, fix the guide and note the fix in its change log.