-
TDD to me is more about Software Design than Development. It gives you a good feedback loop on: - Is what I'm doing going in the right direction? - Did I introduced a regression in the system? - Does the system behave in the way we intend to?Permalink On twitter.com
❤️ 6 Favorites Mood +3 🙂
-
If TDD is about feedback loops, why do we use unit tests to guide our design? Because it's the cheapest way we know of today. If we find a better way, we will adapt, but the methodology will remind. Fast Feedback LoopsOn twitter.com
-
The TDD mindset can be applied to several levels. - Does this method does what I intend it to do? - Does this class ...? - Does this service ...? - Does this controller ...? - Does this microservice ...? - Does this user story ...?Permalink On twitter.com
-
The upper you're, the longer it takes to validate your hypothesis. Still, you can start all the levels with a test. - At the code level, you will use testing frameworks; either for a unit, integration, or e2e testing - At business level, you will use hypothesis and metricsPermalink On twitter.com
-
When you truly understand the TDD mindset, you start asking the right question: "How could I verify faster that I'm going in the right direction?" It's cool to see how you can apply that at Company Strategies, Go To Market Strategies, ...Permalink On twitter.com
-
TDD with unit tests takes a lot to master, but remember to not stop there, and apply the mindset at all levels! Fast feedback loop for you, Fast feedback loop for you too!Permalink On twitter.com