Get the Friday briefing

How we test

Every score starts with a named version, a set test period and our own notes from using the app.

By
Edited by Dale
Updated
[PLACEHOLDER: date]
Article text

Who writes our articles

Our articles are drafted with AI from our own test notes, timings and screenshots. The editor, Dale, checks every article against the app and signs off every score before it goes live. Articles are published under the byline SRS test desk. [DALE TO CONFIRM: Dale will check each article himself, as this says.]

What a test involves

We install the app on the platforms named in the review, and record the version number. We then use it for the jobs a buyer in that section would do: [PLACEHOLDER: the standard task list for each section]. We keep the notes, timings and screenshots that each article is drafted from. Every review states the version, the platforms and the test period. [DALE TO CONFIRM: this describes the practice the site is built to show.]

When we retest

Apps change. When a new version changes something that could move a score, we test it again. A retest adds a line to the review’s score history: the old score, the new score and the reason. [DALE TO CONFIRM: the trigger. Proposal: each new major version.]

What we don’t do

  • We don’t score an app we haven’t used.
  • We don’t take payment to review an app or to change a score. [DALE TO CONFIRM]
  • We don’t send a score to the vendor before it is published. [DALE TO CONFIRM]
  • We don’t use stock or AI-made pictures of software. Screenshots come from our own tests, or from a vendor’s press kit where the vendor allows editorial use. [DALE TO CONFIRM: press-kit images, decision 13]

The full method, with its weights and score bands, is on the How we score page.