Source: https://missionpinball.org/latest/testing/ (archived 2026-10-09; summary of the page text).
- Write automated tests that "play" your game and check the result: simulate a player action
("push start") and validate the state ("was a ball ejected?"), e.g. lane changes by checking LED
states before and after a button press.
- Test-driven development: "you should write your tests before you implement a new feature";
passing tests mean the feature is done.
- Fuzz testing: "automated tests that hit all the switches randomly and make sure MPF doesn't
crash or hang" - recommended early and often.
- "writing good tests will save you time in the long run AND it will make your game more stable."
Linked pages: Running Tests, Writing Tests, the MpfMachineTestCase / MpfGameTestCase / MpfTestCase
API, the virtual and smart virtual platforms, keyboard control, MPF Monitor.