Remove Book Remove Software Review Remove TDD Remove Test-Driven Development
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

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.

Insiders

Sign Up for our Newsletter

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

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. About the Book Club.

article thumbnail

Effective Software Testing – A Developer’s Guide

Henrik Warne

I recently finished Effective Software Testing – A Developer’s Guide by Maurício Aniche , and I really liked it. I have been coding for a long time and I think I have been writing pretty good tests for the features I have implemented. Even so, I found this book quite valuable.

article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. We produce high-quality code in small, verifiable steps. At best, mistakes lead to code that won’t compile. No wonder, then, that software is buggy. TDD isn’t perfect, of course. Why TDD Works.

article thumbnail

5 ways to do Continuously Improved Testing

Xebia

It is okay to start out simple and not overthink, but these two things are key: Have tests – having some tests is better than no tests, as it provides a feedback mechanism for improvement. This results in a steadily-growing set of tests becoming part of the development cycle. Lower-level testing.

Testing 130
article thumbnail

Why Testing is No Longer Sufficient for Today’s Software Delivery Pipelines

OverOps

The move to innovate at speed and scale is stressing software quality and exposing the limitations of testing. Don’t get me wrong – testing in all its forms is inseparable from the software delivery supply chain. The second-order effect here is how it applies to testing.