Custom page

Test Lab playbooks

Borrow the internal scaffolding we use for Playwright and API intensives. Remix responsibly—credit your squad when you fork.

Suite design

Treat suites like city maps: zones for smoke, contract, and experimental probes. We enforce a “no silent skip” rule—every disabled test links to either a ticket or a sunset note in the README ledger.

· Fixture graph sketched before code, not after.
· Quarantine tags expire in three weeks unless renewed.
· Parallel shards named after subway lines for sanity.

Instrument bench metaphor for disciplined suite design

Failure analysis

When red builds hit, use the “three-layer sandwich”: environment fingerprint, data drift check, and assertion truth table. Teams post the sandwich in the incident thread before paging secondaries.

Reporting standards

Bug reports ship with: stable title verb, customer voice impact line, evidence stack (trace id, clip timestamp, log digest), and a “next tester action” so oncoming shifts are not guessing.

We reject reports that hide environment versions in footers—those belong in the lede when reproducibility is uncertain.