If you edit the header, you might notice the comment at the very top that tells you where the unit test is. The point about updating the build system is continue the process away from human- and toward automation-driven validation. Starsha should be able to tell when something doesn't have a test. Starsha should also be able to produce logical descriptions of the corpus, including dependency graphs and testing responsibilities. We can leverage that with the code coverage utility as well. But I am absolutely not refactoring this right now. It is not in scope for this sprint.