Don’t test your implementation.
Jan 12, 2021
You can find me in github now 🎉! https://eduardbargues.github.io/docs/articles/
Sign up to discover human stories that deepen your understanding of the world.
Free
Distraction-free reading. No ads.
Organize your knowledge with lists and highlights.
Tell your story. Find your audience.
Membership
Read member-only stories
Support writers you read most
Earn money for your writing
Listen to audio narrations
Read offline with the Medium app
Written by Eduard Bargues
Proud teacher-volunteer at Migracode and DevOps-engineer at ohpen.com where I keep pushing my AWS+Serverless knowledge every day.
Hello Almantas! Nice that you stoped by to comment on my article.Obviously things are never that simple :D ! This is a (over) simplification of a real REST API with around ~100 tests.About the "components" dependency that you mention, we need to…
--
That is much more maintainable 😊❗
And what about the test velocity to be run?If you have hundreds or even thousands of tests how much time would take to integration test all those tests?That is the benefit of unit testing, the time needed for running those tests is very low.
--
Things aren’t usually as simple as this or even if they are simple now, it might increase in complexity at any moment.If components were any more complex than this, let’s say we depend on a component with an if ststement somewhere, you would need 2…
--
