Testing distributed systems
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain why end-to-end tests across many services do not scale.
Planned topics
- End-to-end tests need every service, database, and broker running: slow to start, slow to run.
- They are brittle: one unrelated outage or data change fails the test, and the failure is hard to locate.
- Environments drift, so results are not repeatable; teams stop trusting them.
- Keep a few end-to-end smoke tests; push most checks lower: unit, integration with Testcontainers, and contract tests.
Draft outline details
Demonstration
a test pyramid for Shop with contract tests between integration and end-to-end.
Check your understanding
Name two reasons end-to-end tests are brittle.
Show answer
Many moving parts and shared environments; any unrelated failure breaks them.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.