LineDepthDeck pageAll guides
E · Optimization & Practice · §18Testing Framework

E · Optimization & Practice · §18

Testing Framework

Track decisions rather than results — opening structure, Legend usage, movement, scoring, interaction, champion choice.

New entry

Mistake taxonomy

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

From the guide — §18 Testing Framework

Opening structure — did the opening four contain a shuffled unit? A two-Energy unit? Did the mulligan produce a functional curve, or was the hand relying too heavily on Silent?

Legend — on what turn was it Empowered? How many empowered retreats occurred, and how many actually led to a second deployment? How many opposing cards or abilities were invalidated? How many points were conceded because of retreat?

Movement — Silent movement triggers, Herder draws, Deadly Weapon damage triggers, Back-Alley Bar bonuses carried elsewhere, and any time Zhonya was mistakenly valued as a movement effect.

Scoring — first scoring window lost, whether you attacked the correct battlefield, whether you preserved a unit instead of a point, whether two-battlefield pressure was available, and whether the opponent successfully concentrated all Might at one location.

Interaction — what Defy countered, whether holding it would have been stronger, whether Not So Fast had a legal high-value target, whether Brynhir was played before or after the important window, and whether Thermo destroyed enough Gear to justify the cost.

Champion selection — would Silent’s protection or +2 have mattered more? Would Deadly Weapon have killed relevant units? Did the switch improve the actual matchup, or merely lower the curve?

Pilot noteClassify each loss as primarily a unit-density failure, a mulligan failure, an incorrect role, a battlefield assignment error, reaction sequencing, a premature Legend Empower, over-retreating, sideboard configuration, a rune or Power bottleneck, or variance.