Over my programming career i’ve heard good and bad things about TDD or BDD. I’ve always liked the concept as it just made sense to me. Write tests to check that your code is valid and that it prevents regression bugs.

Of course, there are some flaws, mostly human/developer flaws, when it comes to TDD. One being that it can take a long time to run all the tests when you have an expansive set tests. Another is that you may not have your data store or environment set up correctly and you wipe out your data store. See my post about how I got the Laravel Testing Database and Testing Environment Setup.

Robert Martin or Uncle Bob gives lots of golden knowledge in this video, but here is what i think we should take away from this video for now.

I love the analogy that TDD is like double entry accounting. It helps me explain the concept to new or even seasoned developers because most everyone can relate to the accounting idea.

I also want to recommend this course to help you get started learning or getting better at TDD.

Thanks for reading. I hope this was useful and if you have a second please share it on social media. I’ve got links below this post to help share it.