article thumbnail

The Real Reasons for Doing Test-Driven Development ??

Xebia

Why do people apply TDD? Here’s a secret: it’s not for the tests. Learn about the actual goal and values hidden under the surface of Test-Driven Development. What Are the Real Reasons for Doing TDD? Test-Driven Development (TDD) is a controversial topic amongst developers.

article thumbnail

TDD saved the day

Xebia

To tackle each operation, I started with a small test, following the principles of Test-Driven Development (TDD). If the tests became too complex, I knew something was missing. For example, when a node is added, it often involves adding a few related relationships. Truly, TDD saved the day!

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Agile Book Club: Test-Driven Development (with Mike “GeePaw” Hill and J.B. Rainsberger)

James Shore

Test-Driven Development is one of the few truly new Agile ideas. In this session, we’re joined by two folks with decades of TDD experience: Mike “GeePaw” Hill and J. In this session, we’re joined by two folks with decades of TDD experience: Mike “GeePaw” Hill and J. Test-Driven Development. ??

article thumbnail

When TDD Is Not a Good Fit

Henrik Warne

I like to use Test-Driven Development (TDD) when coding. However, in some circumstances, TDD is more of a hinderance than a help. Writing tests only makes sense after the solution is viable. Last week, I came across examples of where I developed new functionality without using TDD.

article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

Test-Driven Development. It’s test-driven development, and it actually delivers these results. Test-driven development, , or TDD, is a rapid cycle of testing, coding, and refactoring. Done well, TDD eliminates an entire class of programming errors. Why TDD Works.

article thumbnail

TDD mistakes 2

Habitable Code

Back in 2014 I wrote a blog post listing three mistakes often made by folks who are new to test-driven development (TDD). Writing tests for invented requirements. We’re doing TDD, but we have no code to test; we have nothing to hang our first test on, so we need to invent something, fast!

article thumbnail

TDD: Three easy mistakes

Habitable Code

Back in 2014 I wrote a blog post listing three mistakes often made by folks who are new to test-driven development (TDD). Each time I visit a team that is relatively new to TDD I find the same basic mistakes cropping up every time. Next time, another TDD rookie mistake… Thanks for reading Habitable Code!