How we test

A lab with a copy of every device

A display app has to work with whatever is already in the house. So before anything reaches a tester, it goes through three rounds.

  1. Simulated devices

    For each of the 16 kinds of streamers and 10 amplifier families in the list, a simulated device runs on our network. It announces itself and answers like the real one, including the awkward cases: a device that answers late, drops off the Wi-Fi or reports half a track.

  2. Automated checks on every change

    Each change comes with its own test and is compared with the previous version at tablet, phone and TV screen sizes. A change that breaks a look or a control does not go out.

  3. Real hardware

    Then a tablet and two phones with real music apps and real albums. A tap that should play a track only counts when the right track plays and is still playing thirty seconds later.

The checklist

What we check on every real device

The same fifteen checks for every device we prove, on a tablet and a phone where we can. Each check shows as pass, fail, "not on this model" or "not checked yet". A failing check stays on the site until it is fixed and measured again.

Find

  1. Beside finds the device by itself

Show

  1. Song and artist
  2. Cover
  3. Real format (bits, kHz)
  4. Time runs, and the same song is still playing 30 s later

Control

  1. Play and pause
  2. Next and previous
  3. Volume
  4. Input
  5. Start an album or track on the device
  6. Rooms and groups
  7. Radio and favourites

Hard cases

  1. Wakes from standby
  2. Wi‑Fi drops for a moment
  3. Device restarts

Every proven device has its own report with the result of each check, the date and the firmware. See the list.

What a simulation cannot tell us

Why we ask for test units

A simulated device is built from documentation and from what we have measured. A real one always has a surprise. That is why the list says which brands are proven on real hardware and which are waiting for a test unit.