4 ms·
The only problem I see in the post's story is that the tech lead didn't create a logging standard and reviewed the code to make sure the team followed it. I don
by rubinelli 17y ago
The only problem I see in the post's story is that the tech lead didn't create a logging standard and reviewed the code to make sure the team followed it. I don't see why we should blame debuggers.
- roc 17y agoHe's not blaming the debuggers. He's advocating a step in the build process somewhat akin to dogfooding: encourage he developers to use the tools they've written for support to help find those last few bugs.
- rubinelli 17y agoYou're right. As others said, the title doesn't match the text. Still, I don't think this ad hoc solution is the right one. If your logs are important to run your operations (and if you are processing transactions online, they are,) they should be included in your test plan. Thankfully, the most useful points to log are easy to instrument nowadays with listeners/interceptors/decorators, and sometimes it is just a configuration setting. I just wish it were easier to automate test assertions based on absence/presence of messages in the log.