There are some out there in the industry that will swear by the criticality of test coverage. The conclusion seems to be that 100% test coverage equates to 100% correctness. However, that simply isn't true in all cases.
All posts in Testing
TDD and unit testing in general are HUGE topics, and I'd like to take a dive into the deep end. Read what I have so far.
I really enjoy Go as a language and as a tool for making solutions. A key aspect of getting things done is making sure that a solution works. That's where testing comes in.
There's a huge difference between unit testing, and effective unit testing. I wanted to take the time to clarify such a critical (and often overlooked) practice in development.
I think that by now, most of us in the development community have heard about Test Driven Development and Behavior Driven Development, but how many people do you know that have consistently applied these practices and got the ROI from it?