E · Optimization & Practice · §15Testing Framework

E · Optimization & Practice · §15

Testing Framework

What to log, and the one number that tells you whether the deck is doing its job.

New entry

Mistake taxonomy

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

From the guide . §15 Testing Framework

The log schema for this deck adds two fields most guides do not need: the turn of your first conquest, and how many of your points came from holds rather than conquests.

Turn of first conquest

This is the deck’s health metric. A Lillia deck taking its first point on turn three is doing what it was built to do; one taking its first point on turn six has been playing a game it does not win.

Points from holds

Track it because it tells you whether the seven-unit permanent half is enough. If holds are contributing nothing across a testing block, the argument for cutting Mask and in favour of more real bodies gets stronger, and that is a change worth making on evidence rather than on the reasoning in Section 11 alone.

What to test first

  • Whether does anything, once you have read the card.
  • Whether three is two too many.
  • Whether the second belongs in the main deck against the wide half of the field.
  • Whether earns its two slots, or whether Hidden is not worth the extra Energy over a Fountain.