#tdd

#tdd

Hast mentioned that they trust their unit tests and integration tests individually, and all of them together as a whole. They have no end-to-end tests: We achieved this by using good separation of concerns, modularity, abstraction, low coupling, and high cohesion. These mechanisms go hand in hand with TDD and pair programming. The result is a better domain-driven design with high code quality. Previously, they had more HTTP application integration tests that tested the whole app, but they have moved away from this (or just have some happy cases) to more focused tests that have shorter feedback loops, Hast mentioned.

So far I have: a first draft of the introduction chapter written an outline of the chapters I want to write and for some chapters, some subtopics I want to cover a book landing page a process for building the book a deployment system a way to notify readers of book updates a quick canva-built cover And now I'm ready to hop back to writing. I'm confident all the gears are in place.