Uncle Bob Clean Code Checklist Test Driven Development

https://www.youtube.com/watch?v=58jGpV2Cg50

• Tests are the perfect [[documentation]] for developers.
• When you use tdd:
  • You cannot write code that's hard to write
  • The code is automatically [[decoupled]]
  • You trust the tests
• Separate logic from GUI

Testing is like double-entry bookkeeping instead of assets and liabilities you have tests and production code. Instead of adding liabilities and assets and getting a 0, you get 0 failed tests.

• [[Inheritance]] - test all the lines, each and every parent/child class.
• [[Mutation testing]] - mutates code, expects failure. Makes sure tests actually make assertions.

• Write tests around the solution first.
• Use [[katas]] and tdd excercises to learn this.

• There are two strategies to tdd - [[ouside-in tdd]] (start with HTTP requests and go inwards, acceptance to unit) or [[inside-out tdd]] (starts at the domain/business model and works it's way out to the api, unit to acceptance).

Tests should not mirror code (test class per production code class).