The FIFO testbench
You will learn
What a testbench discipline looks like when it is real, and why this lesson opens the FIFO spec and a mutation recording instead.
A testbench for the asynchronous FIFO would drive both clocks, tear the pointers on purpose and check that the flags never lie. The testbench spec in this tree is not that yet: it does not compile in the browser compiler and native runs are blocked on it, so this lesson opens fifo.t27 itself and, in place of a FIFO testbench, a recording of the discipline it would follow: 5 planted bugs in packets.t27 -- a CRC polynomial bit, a CRC address width, LFRM no-ops, a COR0 bit, a type-2 word count -- each mutant rebuilt and re-swept, every one caught. When a real testbench spec lands, this lesson takes it.