Timeline for Why is TDD not working here?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 3, 2013 at 14:58 | comment | added | Sebastian Redl | At some point you just have to switch on your brain. If you could just add test cases until the inner code suddenly becomes perfect due to some magic refactoring rules, the computer would write the implementation and we could just write tests. | |
| Jul 3, 2013 at 12:40 | history | edited | Odalrick | CC BY-SA 3.0 |
added 601 characters in body
|
| Jul 3, 2013 at 12:12 | comment | added | Odalrick | @TobiMcNamobi As far as I know there is nothing in TDD that says anything about how the refactoring should be done. Usually you refactor for clean code, but nothing says you can't refactor for performance or whatever. Introducing a database isn't something you'd usually do as refactoring. I guess I just don't understand what the question is. | |
| Jul 3, 2013 at 11:12 | comment | added | TobiMcNamobi | Agreed so far. What I still do not get is why should I do the refactoring in a specific way? Using the DB feels more like introducing a new feature - which should be done (as you said) test driven. I can imagine other ways to refactor class A without using the DB. And I cannot drive to use the DB because refactoring means that the test methods do not change. Maybe I should point this out more clearly in the original question. | |
| Jul 3, 2013 at 10:43 | review | First posts | |||
| Jul 3, 2013 at 10:46 | |||||
| Jul 3, 2013 at 10:38 | history | edited | Odalrick | CC BY-SA 3.0 |
added 245 characters in body
|
| Jul 3, 2013 at 10:31 | history | edited | Odalrick | CC BY-SA 3.0 |
added 245 characters in body
|
| Jul 3, 2013 at 10:26 | history | answered | Odalrick | CC BY-SA 3.0 |