<aside> 💡 The traditional "Test Pyramid" suggests balancing unit, integration, and end-to-end tests. Unit tests are focused on individual components. Integration tests test how multiple components work together, and end-to-end tests test the entire system from a user's perspective.

</aside>

E2E tests need to be completely dropped

• Apart from taking a long time to build and maintain, E2E tests execute complete user flows every time on the entire application.
• This requires all services under the hood to be simultaneously brought up (including upstream), even when it is possible to catch the same kind and the same number of failures by testing only a selected group of services—only the ones that have undergone a change.

<aside> 💡 This approach of selecting and testing only a single service at a time is faster, cheaper, and more effective, and can be easily achieved by testing contracts [+data] for each service independently.

</aside>