Test-driven development is a development activity

It’s right in the name

Development.

“What kind of development?” you ask.

Test-driven development. TDD for short.

I hear developers say they don’t have time to write tests. Sure, but you do have time to rewrite it three times and fix the production bugs, but whatever.

Regardless, TDD isn’t “writing tests.” Sure, you produce artifacts called “tests” and run them with testing libraries, but you’re just writing little scripts to exercise parts of your program. Because it’s way faster than manually running your program every time you make a change. And computers are a lot better at comparing values than you are.

Oh, and it helps you discover a usable design for your program too. And that’s probably the biggest win.

tdd 

Like this message? I send out a short email each day to help software development leaders build organizations the deliver value. Join us!


Get the book!

Ready to learn how to build an autonomous, event-sourced microservices-based system? Practical Microservices is the hands-on guidance you've been looking for.

Roll up your sleeves and get ready to build Video Tutorials, the next-gen web-based learning platform. You'll build it as a collection of loosely-coupled autonomous services, developing a message store interface along the way.

When you're done, you'll be ready to contribute to microservices-based projects.

In ebook or in print.