The [review article] isn’t how you would have written it. You’re a developer with battle-tested opinions, and you know you’re right, you just haven’t had the chance to update the Wikipedia page yet to prove it.
@adam I can’t tell from your Facebook profile, but it seems like you might be a software developer, or perhaps a backend developer as opposed to a web dev (specifically front end dev)? What you’re describing seems to match a continuous deployment approach to software dev with a full test suite…?
(un)fortunately this isn’t how all teams approach software development. Some only focus on writing tests for *high value business logic*. Some would argue there are even types of fixes are caused by “untestable” errors (what if I had simply changed the URL, and it wasn’t a bug caused by simply missing the protocol from the URL). And even beyond what you’ve described, some will also write acceptance tests based on the output of an image diff (think wraith). There’s so many ways to add automated tests that it can get quite overwhelming for a team to know where to start. And, sadly, they were well out of scope for my article.
I appreciate you taking the time to put together such a thoughtful comment though about how you’ve integrated automated testing into your workflow. Hopefully you’ll be able to put together a little article with the full details of how you’ve configured the system. It sounds like a fair amount of work for teams and I’m sure there would be a lot of people who would really appreciate your guidance!