Timeline for Can you be Agile without doing TDD (test driven development)?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2014 at 10:29 | vote | accept | CraigTP | ||
| Feb 15, 2013 at 3:04 | comment | added | ShadowChaser | @RobGray Exactly. I almost suspect TDD psychologically appeals to developers - a very rigid structure and process that's code heavy. Everything is a tradeoff, and there are many places TDD would add high overhead - particularly in early phases of development or complex problems that require a high degree of experimentation. Putting TDD style code coverage on every function doesn't make sense and isn't cost effective. It makes the assumption that the integration between the different modules/parts is "perfect", which is incredibly dangerous. Architectural lock in right out of the gate. | |
| Jun 2, 2012 at 7:20 | history | edited | Murph | CC BY-SA 3.0 |
I could hardly resist quoting this as a supporting argument...
|
| Mar 16, 2012 at 5:58 | comment | added | Rob Gray | I've just started work at a large company using SCRUM to run projects. The project I'm working on is SCRUM (correctly!) but the code doesn't have unit tests. Not having unit tests does not effect the ability to use SCRUM or to be Agile, but it does effect my ability to be confident in the quality of the code as well as to quickly make changes (with confidence). Given the lack of documentation that gets produced in Agile, I think writting tests first, last, or in the middle is a massive benefit to remaining Agile (to change). | |
| Nov 30, 2010 at 14:39 | comment | added | CraigTP | "and you might well make an argument that you can't be agile without unit tests (although I suspect that you can be)" - I find this intriguing, I would like to hear more. Given the general acceptance of what it means to "be agile" in the real world, is it possible to be agile without unit tests at all? | |
| Nov 29, 2010 at 14:35 | comment | added | Steven A. Lowe | I have to disagree with this intensely, but with respect to your well-crafted answer. One cannot "be Agile" without actually doing it. And "doing it" pretty much requires TDD. | |
| Nov 29, 2010 at 14:16 | comment | added | Steven A. Lowe | @Marin: no development methods at all are mentioned in the manifesto | |
| Nov 27, 2010 at 13:09 | comment | added | Martin Wickman | @Mcneil: You don't have to write unit tests to "be agile". TDD and UT are great practices by themselves, but not required or even mentioned in the agile manifesto. | |
| Nov 27, 2010 at 10:36 | comment | added | Macneil | Unit tests are required to be agile. It's just that you don't have to write them first. | |
| Nov 27, 2010 at 10:35 | comment | added | user2567 | +1 for this you are agile in the general way you act, not because you use that or that methodology. | |
| Nov 27, 2010 at 10:33 | history | answered | Murph | CC BY-SA 2.5 |