Introduction
In the first part of this series I want to share my personal experience with test-driven development(TDD), how I got there,...
For further actions, you may consider blocking this person and/or reporting abuse
Looking forward to the rest of the series. I wonder if you plan on targeting higher level tests. I mean, unit tests are mostly easy. But how do you test request-to-response with all the middleware, controllers, database and microservices. That has always kept me wondering. How people efficiently do that.
Thanks for the feedback! That's a super interesting topic but maybe beyond the scope of this series. I do plan to talk about acceptance testing when covering outside-in TDD but that's about as high level as I plan to go.
There are a lot of interesting strategies for example something like chaos monkey which turns off random containers to flush out faults.
I will keep this in mind and can maybe do a follow up series!
I tried TDD 5 years ago. I cannot stress enough how powerful it is! It allow me to write code faster and with less bugs. Now whenever I start with a new technology, I first check how to write unit tests :)
Agree 💯. It's hard to go back once you get the hang of it!
Hmm... I see so many tutorials on how to write good tests, but I've never seen one on how to get started with writing tests...
Thanks for the feedback! I can address that in this series. Is there anything specific you'd like me to cover?
One example I can think of is writing tests for a "network" class that sends and receives data.
you got it!
Tdd can be interesting as an exercise in discipline as long as you mean unit tests.
Yes definitely! Higher-level tests are important as well, but that is out of the scope of this series. Albeit acceptance tests that use mostly real objects are an important part of outside-in TDD.
Love to continue the discussion here! Let me know if you agree/disagree or have any questions.