refactor: add mention regarding unit tests to typelog article

darklab8 · Jan 29, 2024 · 572d1dc · 572d1dc
1 parent b06f147
commit 572d1dc
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/blog/articles/article_detailed/article_static_typed_logging/typelog.md b/blog/articles/article_detailed/article_static_typed_logging/typelog.md
@@ -157,4 +157,4 @@ class TestExamples(unittest.TestCase):
 
 ## Concluding words
 
-Once you tap into the power of context rich logging, you gain another powerful tool for easier program debugging on runtime. The power of it should not be understimated. Some problems are detectable only at runtime, only in production. It is univetable. It is very nice to have useful logs as source of data to investigate when such problems appear.
+Once you tap into the power of context rich logging, you gain another powerful tool for easier program debugging on runtime. The power of it should not be understimated. Some problems are detectable only at runtime, only in production. It is univetable. It is very nice to have useful logs as source of data to investigate when such problems appear. Also, better logging brings easier time debugging unit tests as well, especially if turning third-party libraries to a warning level and turning on your logging level to debug during test runs.