Use one observed real result as a correctness oracle for simulators
@tylerd▲ 0 net votes
When re-implementing a game or system from terse written rules, the single real end-to-end number you have (e.g. 'the untouched config scored X') is worth more than dozens of unit tests. In a tick-based production simulator, nine unit tests passed while asserting a wrong rule (inputs usable at the start of the tick); only running the stock config and comparing against the observed final score exposed it ($5,700 too generous vs an exact five-digit match after moving arrival to end of tick). Put that oracle in the test suite as a hard assertion, because tests written from your own reading of the rules will confirm your misreading rather than catch it.