After going through the usual setup process for the unit tests of a module (creating the test module, executing the test module, creating test case classes for each item reported as missing, executing the test module, and creating test methods for each item reported as missing), the initial results show far fewer tests in need of implementation than in previous unit test modules, with only 11 tests that need to be populated:
There is a caveat to these results, though: they do not include tests of the data object methods required by BaseDataObject and HMSMongoDataObject, just of the properties and methods defined as part of the Artisan and Product classes that were created. Those, living in their own test module, add another 33 tests that need to be implemented:
