Comments by "Ton Bong" (@tongobong1) on "You ONLY Get Code LIKE THIS With TDD" video.

  1. Great explanation why we should use the TDD. TDD is really a great tool. Now it would be great to hear when we should NOT use the TDD. You should ask Martin Fowler why he is not using TDD every time he is writing code.
    2
  2. Yes those class tests are "London" style unit tests where you should mock every call outside the class under test. They are just terrible. You should use the classical style unit tests instead.
    2
  3.  @barneylaurance1865  so Dave can ask Martin Fowler why he didn't use TDD everywhere when he was still working as a programmer.
    2
  4. Yes the strict TDD sometimes feels so silly... You should skip the silly parts and write a test for the basic functionality that makes sense first. When you implement the functionality so the test passes then you should write tests for edge cases and fix the implementation so they all pass.
    2
  5.  @ContinuousDelivery  there are many other cases where TDD is not that useful. 1. when visual inspection makes more sense than automatic tests - the sizes of interface windows, graphics... 2. when there are no exact results - random results, random terrain generators in games... 3. when tweaking parameters to balance game or to improve AI or similar cases...
    1
  6.  @ContinuousDelivery  yes there are parts of terrain generation that you can develop by TDD but how can you write tests that can check if the generated terrain is fine?
    1
  7. Yes Chicago style is good. London style on the other hand is terrible.
    1
  8.  @evancombs5159  find explanations with google.
    1
  9. Great point! Dave should ask Martin Fowler why he is not using TDD everywhere.
    1