article thumbnail

Bliki: TestDrivenDevelopment

Martin Fowler

Test-Driven Development (TDD) is a technique for building software that guides software development by writing tests. It was developed by Kent Beck in the late 1990's as part of Extreme Programming. Write the functional code until the test passes.

article thumbnail

The Best Product Engineering Org in the World

James Shore

We use Extreme Programming as our model of how to develop software. They also love test-driven development, pairing, continuous integration, and evolutionary design. They tend to be passionate, senior developers. This is what test-driven development is all about, and its an amazing way to work.

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

My Best Essays

James Shore

Testing Without Mocks: A Pattern Language - 27 Apr, 2018. How to use test-driven development without traditional test doubles. Red-Green-Refactor - 30 Nov, 2005. Test-driven development in a nutshell. An easier, cheaper (and better) way to do continuous integration.

article thumbnail

My Best Essays

James Shore

Testing Without Mocks: A Pattern Language - 27 Apr, 2018. How to use test-driven development without traditional test doubles. Red-Green-Refactor - 30 Nov, 2005. Test-driven development in a nutshell. An easier, cheaper (and better) way to do continuous integration.

article thumbnail

AoAD2 Chapter: Scaling Agility

James Shore

It was created by Craig Larman and Bas Vodde in 2005. Test-Driven Development. If you’re looking for a safe, well-tested approach to scaling Agile, start with LeSS. You’ll need to develop fluency in the Focusing and Delivering zones. I’ll discuss two approaches to doing so: LeSS and FAST.

Agile 117
article thumbnail

AoAD2 Practice: Pair Programming

James Shore

Belshee 2005] reports interesting results from switching every 90 minutes. Test-Driven Development. Take small steps—test-driven development works well—and talk about your assumptions, short-term goals, general direction, and any relevant history of the feature or project. Test-Driven Development.

article thumbnail

The Art of Agile Development, Second Edition

James Shore

So, what allows me to do this—what allows me to do this show, this software development show every week, and what allows me to write this book—is the people who hire me for training and consulting. On February 3rd, 2005, Robert S. Because when you have a large environment, teams often form bottlenecks. A Typical Heavyweight Failure.

Agile 99