Member-only story
6 Problems on Why shouldn’t follow the Test Pyramid in your App
Bending the Clean Architecture Principles
Introduction
One of the major things you will encounter in your development life is Software Testing. Testing nowadays can break or make your application, I have seen teams struggle every day because of tests and others thriving and pushing to production like crazy without any worry.
Just like Maslow’s hierarchy of needs, we standardized our own Testing needs with a Testing Pyramid that we use and apply everywhere.
Our Famous Pyramid
This pyramid comes with a lot of variants including Component Testing, System Testing, Contracts Testing and so on. Also, there’s a huge disparity on how tests should be written and what is a Unit or an Integration Test.
So how should you position yourself in all of this? Does using this pyramid make you the Tests Master? Let’s tackle that!
A Common Use Case
You’re designing an Appointments Management application and you want to stick to this pyramid you love so much. So, you start to meticulously craft your Unit Tests and put everything in isolation. You mocked your infrastructure and added all the tests you can think of.
