Comments by "ForgottenKnight1" (@ForgottenKnight1) on "TDD Revisited - Ian Cooper - NDC Porto 2023" video.

  1. Use DI when needed (like strategy pattern or other patterns where you don't know the concrete dependency before runtime or there can be different dependencies based on conditions in layers above). And stop writing unit tests for internal or private classes. Test public classes, more specifically public methods in those public classes. Mocking couples implementation details to the test, which will make the test fail if you change the implementation, even if the behavior remains the same.
    4
  2. Go read Test Driven Development by Kent Beck. It contains some clarifications to your questions...
    4
  3. Merging development and QA was a very bad decision that corporations made. Now, their agenda is obvious, more profit, but the outcome is software of lower quality. QA is a different mindset than development itself, and having the developer only testing his code is just asking for trouble because of all sorts of biases.
    3