Timeline for In TDD should I have to write Test first or Interface first?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 22, 2016 at 7:12 | comment | added | RubberDuck | Fair enough @gnat that wasn't clear from your comment. Personally, I agree with Nissam here. I find it stops people from using TDD as an excuse not to design at all. YMMV. | |
| Mar 22, 2016 at 6:53 | comment | added | gnat | @RubberDuck I also think so and I believe this is a poor approach. "Until you've done this you should not start thinking about tests..." As I wrote, reasoning in top answer looks more compelling, both in general sense of interface and in the sense of concrete keyword | |
| Mar 22, 2016 at 6:20 | comment | added | RubberDuck | @gnat I believe Nissam here is referring to the C# interface keyword, not the general term "interface". | |
| Mar 21, 2016 at 16:26 | comment | added | gnat | reasoning in top answer looks more compelling: "I don't think you can separate interface design from test design. Defining interactions and designing tests for them are the same mental operation - when I send this information into an interface, I expect a certain result. When something is wrong with my input, I expect this error..." | |
| Mar 21, 2016 at 15:59 | review | Late answers | |||
| Mar 21, 2016 at 16:13 | |||||
| Mar 21, 2016 at 15:44 | review | First posts | |||
| Mar 21, 2016 at 16:27 | |||||
| Mar 21, 2016 at 15:42 | history | answered | Nissim Levy | CC BY-SA 3.0 |