Remove Definition 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

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.

article thumbnail

TDD: Three easy mistakes

Habitable Code

Back in 2014 I wrote a blog post listing three mistakes often made by folks who are new to test-driven development (TDD). Each time I visit a team that is relatively new to TDD I find the same basic mistakes cropping up every time. Writing tests for invented requirements. This is part 1.

article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

Fast, Reliable Tests. Our tests don’t get in our way. Test-Driven Development. Teams who embrace test-driven development accumulate thousands of tests. The more tests you have, the more important speed and reliability become. With TDD, you run the tests as often as one or two times every minute.

article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

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. Done well, TDD eliminates an entire class of programming errors. TDD isn’t perfect, of course. Why TDD Works.

article thumbnail

TDD and Code Coverage Tools

Net Objectives

In TDD and Code Coverage, we established that code coverage tools do not provide useful project metrics, in and of themselves. In TDD, we don’t use code coverage tools for this purpose because we don’t need to. If all production code is written to satisfy prewritten, failing tests, then by definition, all code is covered.

article thumbnail

Don't Measure Unit Test Code Coverage

James Shore

If you're using test-driven development, don't measure unit test code coverage. To improve code and test practices. If you're trying to improve your team's coding and testing practices, perform root-cause analysis 1 of escaped defects, then improve your design and process to prevent that sort of defect from happening again.