A/A test

On this page
  1. Definition
  2. How to compute
  3. Pitfalls
  4. Related

Definition

An A/A test is an experiment where both groups receive the same experience, so the true effect is zero by construction. It does not test the product but the tooling: the correctness of the split, metric computation, standard error estimation, and the pipeline itself.

How to compute

Run it on real traffic before or alongside the main test. The share of “significant” differences at α=0.05\alpha = 0.05 should be around 5%, and p-values should be uniformly distributed. Also inspect SRM and metric stability day by day. For every new metric type an A/A run is worthwhile, at least on historical data.

Pitfalls

An A/A test cannot catch an error specific to a particular variant; it validates only the shared infrastructure. A passed A/A does not guarantee correctness under a real effect. Spending all traffic on it steals power from useful tests. A single A/A run without a SRM check proves little.

Related terms

Mentioned in

Connections map

Terms, articles and projects connected to this concept. Hover a node to see its name; click to open.

← All terms