Skip to content

Only on this base

On top of the counterparts to the usual CI actions, this base has things of its own.

Building the e2e environment itself

  • For every run, the whole environment under test (including Android) is prepared, and discarded when the run ends
  • It is not a standing machine that gets reused. Building the environment is part of the system

The gate

  • Changes are verified in the “future state” — the line of changes as they will be merged — and only what passes lands
  • A change that fails is removed, and the rest is rebuilt and verified again (see “How gating works”)

The promotion set

  • The flow that raises develop to qa is itself a set flow and a set of jobs (see “The promotion flow”)

Complexity and evidence

  • There is a dedicated mechanism that measures, and leaves the numbers and screenshots as evidence (see “Complexity and evidence”)

Verifying bundles across repositories

  • Related changes can be grouped across repositories and verified in their combined state