@manton Claude is pretty good at writing tests…
I am a firm believer that tests tell you what the code should do, and the code itself and docs tells you how it’s accomplishing that goal. When you don’t have tests, you have no idea what the behavior should be. If you don’t have tests, you should be adding them as you work on parts of the code to enshrine your understanding of what you should be accomplishing. Every bug is ultimately undocumented behavior where your users tell you that you were either wrong about what should happen or what should happen was undefined. The bug report itself tells you there’s a part of the should that is in that state, and tests are the best way to document the decision on what should happen and ensure that this behavior is maintained until that decision is changed.
Something I wrote the other day. I will, one day, convince indie developers who spent a lot of time in Objective C to write tests.