Hi Simon, > How about an aggregated trick, incrementally hashing each output crc value > and at the end just compare the hash against an expected value? Instead of > comparing each incremental crc value against a table.
While this needs fewer expected values, it makes debugging harder in case of a failure. Unit tests frequently fail during development, and I find it very useful to be able to debug the particular failing step directly, using gdb. Delaying a failure until the end of the computation makes debugging hard. Bruno
