3 ms·

I love clean and well-written code but to achieve clean code we should be able to refactoring without break our code. This is the point for TDD.

• _pmf_ 13y ago
  > I love clean and well-written code but to achieve clean code we should be able to refactoring without break our code. This is the point for TDD. That's also true for vanilla regression tests. There's nothing special that TDD adds in this regard.
  • pauloortins 13y ago
    I disagree with you at this point. When using TDD we tend to do a better code design and we avoid to write unnecessary code. Take a loot at http://www.ime.usp.br/~aniche/files/tdd-and-design-draft.pdf http://www.ime.usp.br/~aniche/files/tdd-and-design-draft.pdf
    • stonemetal 13y ago
      Take a loot at What are we supposed to be looking at there? Like most TDD literature I see a lot of assertions, but no evidence to back it up.
      • pauloortins 13y ago
        What would be a good evidence for you about the TDD influence in design ?
        • stonemetal 13y ago
          Me personally, I would take several projects with TDD and non TDD methodologies, control variables like team size, project size, team experience, etc. and compare outcomes like defects rates, schedules, performance, etc. Try looking at SEED http://evidencebasedse.com/ http://evidencebasedse.com/ . TDD comes out not to bad. Quality correlates very well with # of unit tests regardless of methodology. TDDers tend to have more unit tests. Therefore TDD tends to produce quality code at better rates than other methodologies because it tends to produce more tests.