File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Testing and the fly likes TDD and the development process Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Testing
Bookmark "TDD and the development process" Watch "TDD and the development process" New topic

TDD and the development process

Allan Halme
Ranch Hand

Joined: Aug 22, 2003
Posts: 62

How much or what parts of the value of using TDD is dependent on the development process being agile or iterative, as opposed to a more waterfall-based approach, which may indeed have a "unit testing phase" (that a previous poster mentioned)?

(Assuming that the process isn't so strict that it actually enforces coding production code first and then producing unit tests after the fact, but allows development and unit testing to proceed simultaneously.)

<i>The lyf so short, the craft so long to lerne.</i> --Geoffrey Chaucer (c. 1343-1400)
Lasse Koskela

Joined: Jan 23, 2002
Posts: 11962
To make a blanket statement, I'd say that the overall development process doesn't matter--you can still use TDD and benefit from it. It's just that the effects of TDD might be hidden by the bigger improvements or problems brought forth by the development process.

I'm curious about what you're thinking? Do you have a differing argument in mind?

Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
I agree. Here's the link:
subject: TDD and the development process
It's not a secret anymore!