Why I Recommend TDD


TDD is great for large applications, TDD is great for teams. The only time not to use TDD is if you're just beginning with coding. If you understand the basics, move to TDD next. For those of you ready to learn about TDD here are some great articles I either found or had referred to me.

Difference Between TDD and BDD - A Helpful Stack Overflow Answer

written by jackson


I take this back a little bit

Mar 9, 2017

I take this back a little bit because of the pros / cons

For an agile developer like me TDD seems to be a waste. I like to let the development experience steer me to realize where the project's full potential is. That's how the best projects are made IMO.

That being said, on big agile projects I HIGHLY recommend implemented TDD after the fact. That way any tweaks / changes / updates won't break your code base. You've got to have tests.

If you're doing waterfall dev on a large project then TDD makes sense from the get-go.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <p> <pre>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.
  • E-Mail addresses are hidden with reCAPTCHA Mailhide.

More information about formatting options

Complete this form and then pat yourself on the back.