@housecor At first you should be writing down a list of behaviours you want your code to achieve. That limits what your API can become and that’s where TDD comes in
@ceilfors Chapter 1 of the @KentBeck book which started it all. It seems to be skipped by most tutorials on TDD which promotes the impression that you start with no up front design and just write tests. This was never the case. Up front ‘design’ is the first step all driven by a behaviour.
@davidsmorais@epoch_rift@vitest_dev Just read your article. Good stuff. Would say that using TDD to test a framework is kinda of an anti-pattern, should only be using TDD for code you write as have to assume the framework has its own test suite. Far less frustrating using it only on what you own
@unclebobmartin I'm reading the refactoring chapter in #cleancraftsmanship and your example using the csv/report builder has me confused. You split a class into two where one inherits from the other, isn't this a Liskov Substitution Principle no-no?? Please enlighten.