Tests are very much a "if you liked it then you shoulda put a test on it" thing. If some end-user property is desirable to you, make sure a test covers it so th

Tests are very much a "if you liked it then you shoulda put a test on it" thing. If some end-user property is desirable to you, make sure a test covers it so that you can be sure it still works that way. This is a godsend when doing extensive refactors on the codebase, which lets you move fast. https://twitter.com/simonw/status/1701764953114546664 https://twitter.com/simonw/status/1701764953114546664: "The single biggest productivity enhancement I've ever found for my own personal projects is writing comprehensive tests for them. I don't mean TDD - I rarely write tests first - I mean trying to never land a feature or fix a bug without a test that proves that it works" > No tests that click through the UI and screenshot and compare and hit the network. That's fair, I think testing UI is just hard in general and it's easier to rely on users to submit bug reports especially if the UI rarely breaks.