From the course: Test-Driven Development in Django

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

TDD vs. test after

TDD vs. test after

From the course: Test-Driven Development in Django

Start my 1-month free trial

TDD vs. test after

- [Presenter] While test-driven development is great, there's some legitimate criticisms against it, especially why you wouldn't use it early on in a project. So, with tests, they can definitely take away joy, motivation and the speed at which you program. Having to always having to write a test before you do anything can be exhausting. When a project is young, it changes so much that really, you might ask is there that much of a need for testing if you're always going to be changing features, and sometimes you end up deleting features. If you've written a million tests for this one special feature and then you end up not using that feature, then what was the point of writing all of those tests? The basic idea is if others aren't using it, what's the purpose in testing? You don't need to guarantee that everything is working. So if you subscribe to this philosophy, or any of these things are ringing true with you, then here's what I'd recommend if you're going to be adding tests later…

Contents