This is ~5 minutes pitch on which I share a few thoughts about good & bad practices we committed when it comes to coding blau, how those affected our tests, a few useful tools we found during the process and other cool stuff!
information/state that may change as program execution proceeds, nor can it depend on any external input from I/O devices ✓ evaluation of the result does not cause any semantically observable side effect or output, such as mutation of mutable objects or output to I/O devices.
graphics hardware, input timings, the frame rate) ✓ much of the output is hard to measure (e.g. on- screen graphics, sound effects) ✓ OTHER PARTS ARE almost meaningless outside of the full game context making (eg. complex reactive AI, physics simulations).