article thumbnail

TDD or Test-Last? One Thing at a Time

Xebia

That is precisely what TDD helps with. TDD to Separate Concerns At the core of TDD is its mantra : red, green, refactor. " Red is where we express our understanding of the problem in a failing test, one piece at a time. We’re fleshing out the problem piecemeal, specifying behavior we want of the system.

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. This description takes the form of a test. Then, you implement a portion of the code that fulfills the test’s requirements.

Insiders

Sign Up for our Newsletter

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

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. Feedback on what?

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. Avoiding Premature Tests.

article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

We see the same kinda thing with unit testing. Clearly, the best way to test any software is with fully automated ‘systemtesting that is thorough enough that it can be used for full regression testing. So, unit tests are great for ensuring that a few components amongst the whole set, have good quality.

article thumbnail

TDD and System Architecture

Net Objectives

When first adopting TDD, developers can run into some roadblocks that seem to indicate that TDD is a difficult process. In truth, some of these problems actually indicate faults in the system architecture.

article thumbnail

TDD and Test Anatomy

Net Objectives

TDD, when conducted as a specifying activity, is an aspect of Behavior-Driven Development (BDD). Behavior is what we specify and is what we “drive” into the system using tests. Therefore, when structuring the tests in TDD we can be guided by the language of BDD: Given, When, Then.