Remove Examples Remove Systems Review Remove Test-Driven Development Remove Testing
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. This description takes the form of a test. The tests didn’t make assumptions about the inner workings of the code.

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

AoAD2 Practice: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. 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. 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

5 ways to do Continuously Improved Testing

Xebia

In many organizations, automated testing lags behind and becomes a bottleneck for successful continuous delivery. Either tests do not provide enough confidence or companies take a very traditional approach, resulting in releases either introducing substantial risks or becoming costly. These principles tell us our tests should be: Fast.

Testing 130
article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

As a great example, Stand-ups always come to mind. A big problem in development, particularly when a lot of people are introverts, is communication. We see the same kinda thing with unit testing. So, unit tests are great for ensuring that a few components amongst the whole set, have good quality. But it got worse.

article thumbnail

Why Dumb Tests are Smart ?

Xebia

Writing tests that help evolve a system is hard, and you get there by avoiding smart tests while preferring dumb ones. The Paradox of Smart Tests Smart is always better than dumb, isn’t it? This time we’ll look at the paradox that dumb programmer tests are superior to smart ones. Let’s dive in.

Testing 130