3 ms·

First thing: they do not define which kind of TDD they are talking about. Second thing: without really good test coverage any kind of larger refactoring is gamb

by yoz-y 7y ago

First thing: they do not define which kind of TDD they are talking about. Second thing: without really good test coverage any kind of larger refactoring is gambling with reliability and will bite you at some point.

gtirloni 7y ago
What kind of TDDs are out there? Don't seem fair to call out author on not writing tests because they never said that.
- yoz-y 7y ago
  > What kind of TDDs are out there? I have never actually seen somebody writing all of the tests before implementing the code even if they claimed doing TDD. Parts of tests maybe but I think that things rarely go the way the definition is spelled out. > Don't seem fair to call out author on not writing tests because they never said that. Fair point. I have written my comment halfway into the article, the author makes a point about tests at the end.
  - oriolid 7y ago
    > I have never actually seen somebody writing all of the tests before implementing the code even if they claimed doing TDD. I had an architect who did exactly this. It was awesome, one could just look at his code and see where it would fail because it didn't occur to him to either test for that case or actually think what the code does. His only explanation would be "but it passes the tests". Later he was made into CTO. In a way, not testing for edge cases that are found during development is quite similar to commenting on article one hasn't fully read.
- nurettin 7y ago
  Right, I write tests for existing functionality. And I decide what test to write after I write code. In the spirit of this article, I would assert that a simple two line integration test could cover a large portion of code depending on how many parts it requires to work together correctly.
- spdionis 7y ago
  https://github.com/testdouble/contributing-tests/wiki/Test-Driven-Development https://github.com/testdouble/contributing-tests/wiki/Test-D... This wiki has great content about the different types of TDD. Reading it helped me get useful insights about my approach and my gripes with TDD. In particular it's interesting how different approaches to testing influence heavily the design of your code.
- UK-Al05 7y ago
  London school, Chicago school, outside in, inside out. Sociable unit tests, solitary unit tests, state verification, behaviour verification and so on There are so many attributes.

by yoz-y 7y ago

gtirloni 7y ago

What kind of TDDs are out there? Don't seem fair to call out author on not writing tests because they never said that.

yoz-y 7y ago
> What kind of TDDs are out there? I have never actually seen somebody writing all of the tests before implementing the code even if they claimed doing TDD. Parts of tests maybe but I think that things rarely go the way the definition is spelled out. > Don't seem fair to call out author on not writing tests because they never said that. Fair point. I have written my comment halfway into the article, the author makes a point about tests at the end.
- oriolid 7y ago
  > I have never actually seen somebody writing all of the tests before implementing the code even if they claimed doing TDD. I had an architect who did exactly this. It was awesome, one could just look at his code and see where it would fail because it didn't occur to him to either test for that case or actually think what the code does. His only explanation would be "but it passes the tests". Later he was made into CTO. In a way, not testing for edge cases that are found during development is quite similar to commenting on article one hasn't fully read.
nurettin 7y ago
Right, I write tests for existing functionality. And I decide what test to write after I write code. In the spirit of this article, I would assert that a simple two line integration test could cover a large portion of code depending on how many parts it requires to work together correctly.
spdionis 7y ago
https://github.com/testdouble/contributing-tests/wiki/Test-Driven-Development https://github.com/testdouble/contributing-tests/wiki/Test-D... This wiki has great content about the different types of TDD. Reading it helped me get useful insights about my approach and my gripes with TDD. In particular it's interesting how different approaches to testing influence heavily the design of your code.
UK-Al05 7y ago
London school, Chicago school, outside in, inside out. Sociable unit tests, solitary unit tests, state verification, behaviour verification and so on There are so many attributes.