After the initial unit test setup, there are 74 tests that need to be implemented, largely due to the overrides of properties and their setter and deleter methods from their Base counterpart classes in hms_core. Since the main difference between the properties and their overridden methods is the inclusion of an automatic change in the instance's is_dirty property during a set or delete call, that might appear to be the only thing that the property-related tests at this level need to be concerned with:
The tests for the properties are all close to the standard structure that has been used so far, essentially ...