As discussed in #15 Debug.log messages appeared during the run of tests mixed in with the progress messages.
This change delays output of Debug.log messages such that they are emitted after all of the tests have completed and appear in context of which test produced them.
Coverage remained the same at 100.0% when pulling 81dacf3451997dfa33740ab8e52e80c3a888158c on improve_debug_logging into 9d8351114aafa83296c714d8db25ece749c9f582 on master.
Coverage remained the same at 100.0% when pulling 900bf1fe69e8a610a33f5ea0b4b5b23252dee829 on improve_debug_logging into 9d8351114aafa83296c714d8db25ece749c9f582 on master.
As discussed in #15 Debug.log messages appeared during the run of tests mixed in with the progress messages.
This change delays output of Debug.log messages such that they are emitted after all of the tests have completed and appear in context of which test produced them.