HANDS-ON TEST METHOD 1.2.0

How we test espresso equipment.

See the steps, repeat counts, measuring tools, raw-data rules, and review checks used before we publish a hands-on result. This method was published on 2026-07-24.

ER / TEST METHOD SUMMARYVERSION 1.2.0
TEST SECTIONS09
PLANNEDTEST METHOD 1.2.0
Method date
2026-07-24
Checks before publishing
6
Questions waiting
08
Required reviewers
2
SCHEMA 1.2.0UPDATED 2026-07-24

TEST STEPS / METHOD 1.2.0

Every result must pass every required check.

A machine and a grinder need some different steps. Both tests check product identity, space, daily use, sound, electricity, and clean-up. Other steps cover the parts unique to each product. The repeat counts are minimums.

  1. IDMACHINE AND GRINDER

    Check the exact product

    Record the model, public SKU, hardware version, region, voltage, source, and a protected serial code before the result can link to a catalog product.

    Minimum
    1 check
    What we publish
    Product identity and hardware version
  2. FITMACHINE AND GRINDER

    Measure space needed to use it

    Measure stored size, working clearance, cable and hose reach, and the space needed to load, fill, and clean the product.

    Minimum
    3 runs
    What we publish
    Stored size and space needed to use it
  3. FLOWMACHINE AND GRINDER

    Time the daily steps

    Time a repeatable start-to-finish task from a cold, reset station. Include every step the product needs, not only one part of the task.

    Minimum
    5 runs
    What we publish
    Typical task time and interruptions
  4. BREWMACHINE

    See how steady each shot is

    Use the same coffee, grinder, basket, dose, drink weight, preparation steps, and measured shot path for each shot. This shows consistency; it is not a universal taste score.

    Minimum
    10 runs
    What we publish
    Shot temperature and drink-weight range
  5. MILKMACHINE

    See how fast milk heats

    Heat the same amount of cold milk to the same stop temperature. Record time, time before steam works again, and the steps needed for each cycle.

    Minimum
    5 runs
    What we publish
    Milk heating time, restart time, and daily-step notes
  6. DOSEGRINDER

    See how much coffee comes out

    Follow the stated seasoning and purge steps. Measure the coffee in, coffee out, time, and coffee left behind across repeated doses.

    Minimum
    10 runs
    What we publish
    Coffee-in, coffee-out, and grind time
  7. CTRLGRINDER

    Check grinder adjustment

    Measure how ground coffee and shot flow change at set adjustment points. Keep the coffee, dose, preparation, machine, and target drink weight the same.

    Minimum
    10 runs
    What we publish
    Grinder response and useful shot range
  8. LOADMACHINE AND GRINDER

    Measure sound and electricity

    Measure sound at a fixed distance and electricity used during the task. Record the room background sound and test length with every value.

    Minimum
    5 runs
    What we publish
    Task sound level and electricity used
  9. RESETMACHINE AND GRINDER

    Reset the station

    Reset the station from a used state. Record routine cleaning, access, supplies, time, mess left behind, and any model-specific limit in the manual.

    Minimum
    5 runs
    What we publish
    Reset time, supplies, and access notes

CHECKS BEFORE PUBLISHING / INCOMPLETE RESULTS STAY PRIVATE

We do not publish a result with missing information.

Interrupted or conflicting runs can stay in the test log. They cannot become a public hands-on result until the record is complete. Each requirement is checked before publication.

  1. 01

    Exact productPublic SKU, hardware version, U.S. voltage, how we got it, and a protected serial code.

  2. 02

    All required test stepsA good result in one area cannot replace the full test.

  3. 03

    Calibrated measuring toolsTool identity, purpose, units, and calibration check come before the test.

  4. 04

    Minimum repeatsTest conditions and run order stay with every summary number.

  5. 05

    Raw data and limitsEvery published number can be recalculated from frozen raw repetitions, meaning the individual measurements, in a data package at a stable path. A verified checksum is a code that shows the package has not changed.

  6. 06

    Two-person reviewTwo named reviewers must be different from each other and from the tester. Corrections replace a result; they do not hide its history.

EVIDENCE LABELS

Four labels. Four kinds of information.

Source

Published product detail

A manufacturer or authorized retailer published the detail. Espresso Receipt checked the source and date.

Our summary

Our explanation

A fit or daily-step judgment based on cited product details.

Estimated

Calculated estimate

A shown formula produced the value from visible inputs.

Hands-on test

Hands-on test

An identified physical unit completed this method. The record includes conditions, repeats, tools, raw data, and limits.

VERSIONS AND DATA HISTORY

Test method 1.2.0 · data format 1.2.0 · published 2026-07-24.

The method version says how we run a test. The data format version says which fields a published result contains. A change to either one starts a new record instead of changing an old record. The public data file includes both versions, the test steps, and the waiting list.