Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Why Don’t You Practice Test First Development?

DZone's Guide to

Why Don’t You Practice Test First Development?

· DevOps Zone ·
Free Resource

In response to accelerated release cycles, a new set of testing capabilities is now required to deliver quality at speed. This is why there is a shake-up in the testing tools landscape—and a new leader has emerged in the just released Gartner Magic Quadrant for Software Test Automation.

 I would have said “Test Driven Development” but I want to make it clear that what I’m talking about is writing test first, or at least simultaneous to writing the code.  Not sometime after, even if that after is immediately after.

Recently, I’ve been doing some Test First Development presentations and I’m finding a trend that I’d like for you to contribute more information to.  While just about everyone I talk to will say they believe that we should be practicing Test First Development, hardly anyone is actually doing it practicing Test First Development.

So, the question I have to ask is, “Why?”

So, leave me a comment and tell me why you aren’t writing test code first.

Gartner: Digital Transformation, DevOps, and the Future of Testing. Download Now! 

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}