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

Sometimes, the coding task in front of you can be overwhelmingly complex. Armed with a few assumptions about how things should work, I embarked on developing an application with a graphical UI and a backend. To tackle each operation, I started with a small test, following the principles of Test-Driven Development (TDD).

Insiders

Sign Up for our Newsletter

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

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. Originally created by Kent Beck as part of Extreme Programming, it’s a fantastic way of making sure your code does what you intended it to do. It’s not perfect, but it’s a powerful tool for creating robust and reliable software. Rainsberger.

article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. We produce high-quality code in small, verifiable steps. At best, mistakes lead to code that won’t compile. No wonder, then, that software is buggy. TDD isn’t perfect, of course. Why TDD Works.

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

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

It all has to be very reactive; you keep fiddling with the code until it gets traction. Under those conditions, it doesn’t make sense to cross all the t’s and dot the i’s as the life expectancy of the code is weeks or months. As a great example, Stand-ups always come to mind. We see the same kinda thing with unit testing.

article thumbnail

TDD mistakes 3

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. Writing a dozen or more lines of code to get to GREEN. It is also not TDD. Let’s look at an example.