You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you @stemmlerjs for putting that together. That repo and your courses are the most applied, reusable piece of teaching I've found on the DDD matters.
However, while you go in great lengths about architectural concerns, I was surprised by how few unit tests there are in your code repository. Usually, TDD is a good companion to DDD. Do you have thoughts to share about it ?
The text was updated successfully, but these errors were encountered:
@TheWinch, thank you! I certainly do have opinions about this that you'll hear very soon. I've been studying and experimenting with this. I'm currently working on Chapter 3 of solidbook.io, which includes a discussion and demonstration of TDD, BDD, and Extreme Programming principles & practices in detail.
Long story short, I believe in the XP practice of writing the failing customer tests first (which will look a lot like BDD - some also call these "acceptance tests"). It is so beneficial to get your testing architecture and your customer tests set up early on in the project. That's something I regret not doing earlier because it influences how you write testable application layer use cases.
I haven't followed my own advice here; I was still very much in the process of research, experimentation, and deciding upon the philosophy for testing that I want to preach (in addition to writing about my decisions) when I was assembling this codebase.
Thank you @TheWinch, again, for your comment, your patience, and your support. Please stay tuned for an email from me on:
BDD, TDD, and XP principles in practice in Chapter 3
updates to this codebase
a revised version of Chapter 11 which will walk you through TDD applied here in DDDForum
Hello,
First of all, thank you @stemmlerjs for putting that together. That repo and your courses are the most applied, reusable piece of teaching I've found on the DDD matters.
However, while you go in great lengths about architectural concerns, I was surprised by how few unit tests there are in your code repository. Usually, TDD is a good companion to DDD. Do you have thoughts to share about it ?
The text was updated successfully, but these errors were encountered: