Testing Framework

What to log, so the answers to the open questions come from games rather than from opinion.

Match checklist Testing log Condensed pilot card

New entry

Opponent deckPlay or drawResultTurns with two or more spellsPump held rather than cast, and what forWhat answered your first threatBurn spent on creatures vs faceSequencing mistakes

Mistake taxonomy

Stored in this browser only : no account, no backend, no upload.

From the guide . §17 Testing Framework

Two things are worth logging with this deck and most others are not: how many turns contained two or more spells, and what answered your first threat.

The first tells you whether the engine is working. The second tells you what the matchup actually is, and it is the field evidence that either supports or overturns the pump argument in §12.