The bare-bones starting point for the collection of tests just shown would work as a starting point for any other collection of tests that are concerned with a single module. The expected code structure for hms_sys, however, includes whole packages of code, and may include packages inside those packages. We don't know yet, because we haven't gotten that far. That's going to have an impact on the final unit testing approach, as well as on the creation of template files to make the creation of those test modules faster and less error-prone.
The main impact is centered around the idea that we want to be able to execute all of the tests for an entire project with a single call, while at the same time not being ...
