In article <[email protected]>, "Armistead, Jason" <[email protected]> writes:
> One potential problem would be accounting for any variation in the > execution behavior, e.g. if the time-of-day clock was read from the host > or if network in teractions occur (assuming networking is enabled). Properly written unit tests can avoid this problem by providing test doubles for the subsystem that introduces variation (clock, network, disk, etc.). The last time I looked at the source code for SIMH, I was surprised that it had zero unit tests (still the case in version 3.8-1). That makes it hard for others to contribute (how do I know I didn't break something at a distance?) and difficult to know with any certainty that any of these emulations are correct. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com> _______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
