Remove Agile Remove Software Review Remove TDD 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. Feedback on what?

article thumbnail

Bliki: TestDrivenDevelopment

Martin Fowler

Test-Driven Development (TDD) is a technique for building software that guides software development by writing tests. In essence we follow three simple steps repeatedly: Write a test for the next bit of functionality you want to add. Write the functional code until the test passes.

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

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

When the Agile Manifesto came out 20 years ago, I really liked what it said. It all has to be very reactive; you keep fiddling with the code until it gets traction. Startups were quite agile long before the manifesto used that term. In order to sell its ideas to corporations, Agile ended up formalizing itself.

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. Test-Driven Development. ??

article thumbnail

Test Driving and Unit Testing Thread Safety

Agile Alliance

This session shows how to use TDD to drive the design of a multithreaded code. If you've confronted test driving for thread-safety this session is for you.

article thumbnail

It’s never too late to add unit tests to legacy code

TechBeacon

Most developers believe in the value of unit tests, even if they don't always like writing them. Most of them are okay with writing unit tests while doing new development work or practicing test-driven development (TDD), but it's easy to be disciplined with greenfield development.

article thumbnail

TDD: primitive obsession ( part 3 )

Apiumhub

Last month we talked about TDD example in software development ( part 1 ) and TDD first cycle ( part 2 ). In this new TDD and primitive obsession article, we will focus on removing duplication and reinforcing the constructors of our entities, something key to have a robust system. TDD: primitive obsession.