The bulk of the unit tests that need to be implemented fall fairly neatly into the standard processes that have been in play since the beginning of the hms_sys development effort, and there's nothing new to say about those. A relatively small number of others, however, have some noteworthy variations.
With the advent of a substantial amount of new code that relies heavily on either standard Python modules (atexit, logging, and signal, for example, in the daemons codebases), or various third-party modules that were installed to meet specific needs (pika, for RabbitMQ support), another aspect of testing policy bubbles up: the question of how deeply (or even whether) to test functionality that are little more ...
