Unit testing a TCP stack (2015)
There&#x27;s a lot of push back from engineers - especially people at lower levels of the stack - against testing infrastructure. One particularly famous example is Linux. Rather than testing before merging in code, they merge in code and then test the release candidate as a whole. It also seems game developers are extremely against automated testing frameworks as a whole. I&#x27;ve heard many times that it would be impossible to develop an enemy AI in a test-driven way (I did this for a senior project in college - finished the AI before the game was able to even start testing it [0]).<p>I wonder what would need to happen to convince people that:<p>1. Even if you do something extremely low level, you can draw a distinction between your hardware and the interface that 99% of your software runs at.<p>2. You can develop complex behaviors iteratively  with automated testing just like you can develop complex programs iteratively (tests are just programs).<p>[0] - <a href="https:&#x2F;&#x2F;github.com&#x2F;gravypod&#x2F;it491-disabler-ai" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;gravypod&#x2F;it491-disabler-ai</a>