Writing tests alone is not enough.
I'm developing
RocketSim in my spare time, and especially for side projects, it's sometimes challenging to keep writing tests. Time is limited, so if you have time, you want to move fast and work on new features instead.
I've shared
Side Projects: 10 Tips for being successful before, in which you can learn how I like to work on my side projects. One thing it doesn't cover is how you should deal with tests.
Last week, I released RocketSim 12.0.0 (more on that next week) with the idea of "Ship fast, learn fast." Unfortunately, I went a little too fast since I broke the recording functionality, even though one of my tests would've told me before releasing.
Since I work solely, I don't have PRs and CI runs for changes. That decision made me forget to do a final unit test run (oops). On top of that, since it's a side project, I had to wait till I was done working at WeTransfer before I could work on a fix.
In other words, make sure to write tests for crucial parts, but also make sure not to forget to run them before a release (it sounds so obvious when I'm writing this now)
Enjoy this week's SwiftLee Weekly!