A naukri.com initiative
Dev
2w
17
Image Credit: Dev
Shifting End-to-End Testing Left on Microservices
- Developers should get test feedback sooner in order to write code faster and see how it works earlier.
- In microservice development, developers are often writing code they can’t run without a full test suite and so full tests must run early.
- At Earnest, every developer can run ultra-fast end-to-end tests that are usually run by QA, allowing for swift feedback.
- Uber developed the Backend Integration Testing Strategy to handle the complexity of its microservices architecture.
- This involves using isolated sandboxes, smart routing, tenancy-based data filtering and sandboxed Kafka integrations to mirror production as closely as possible.
- They also use the Composable Testing Framework which produces modular test flows that simulate complex scenarios which reduces maintenance overhead and aligns tests with real-world use cases.
- Advanced test management and analytics help to track test health, endpoint coverage and failure patterns and automatically quarantine unreliable tests.
- Uber has reduced incidents by 71% per 1,000 code changes by utilizing these practices, emphasizing the importance of the collaboration and communication of testing amongst teams.
- E2E testing is impractical for microservices with the complexity and variability they introduce. Tools like Signadot provide lightweight sandboxes for early testing, helping to catch potential errors early.
- Using effective tools for fast, reliable, and scalable testing will ensure the shift of E2E testing left in Microservices is successful.
Read Full Article
1 Like
For uninterrupted reading, download the app