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 was convenient as it allowed me to maintain a TDD flow without external dependencies. 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

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

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

Xebians collaborating on internal tool development

Xebia

One such initiative involves developing a toolset for assessing a customer’s situation. This toolset (working title: Truffleswine) allows us to retrieve relevant data from systems quickly, which in turn helps us ask the right questions sooner and clarify business cases for improvement using actual data.

article thumbnail

A Next Step Beyond Test Driven Development

Honeycomb

The most successful software development movement of my lifetime is probably test-driven development or TDD. With TDD, requirements are turned into very specific test cases, then the code is improved so the tests pass. That step is observability driven development.

article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

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. In its fullest form, it is at least as much code as the thing it is going to test, and you have to build a custom version of it, every time, for every system.