> but if you do find a bug, you write a new test and fix it.
Maybe there's a misunderstanding here but this library is not meant to replace tests. It's for initially finding the bug for which you then write a test case (or not).
> but if you do find a bug, you write a new test and fix it.
Maybe there's a misunderstanding here but this library is not meant to replace tests. It's for initially finding the bug for which you then write a test case (or not).
It isn't clear how this library helps one find bugs.
If you're not sure how logging debug information can help you find bugs then I'm not sure what to say. Especially if you've been programming for four decades, I would think it would be obvious how logging information can help you find logic or data errors in your code/inputs/outputs.
I know how to write failing tests, and use a debugger.