Downloaded 16 times
Uploaded byUri Goldstein
Testing microservices
The document discusses a layered approach for testing microservices architectures, including unit tests that target individual units, integration tests that focus on communication interfaces, component tests that test entire microservices, contract tests that verify interface contracts, and end-to-end tests that validate overall system functionality by testing without mocks. Each layer of testing has distinct benefits and use cases to ensure quality across the microservices architecture.
More Related Content
Testing microservices
- 1.
- 2. SOURCE & CREDIT TestingStrategies in a Microservice Architecture / Toby Clemson https://martinfowler.com/articles/microservice-testing/
- 3. GOAL •Learn a layeredapproach for building an automated test strategy that ensures the quality of a microservices architecture
- 4. CHALLENGES • Network Partition •Communication Failure • Fragile Contracts
- 5.
- 6. FIVE LAYERS • Unit •Integration • Component • Contract • End to End
- 7. UNIT TESTS • Target:Units • Benefits: • Fastest feedback • Improved design • Use cases: • TDD • Business logic • Edge cases in comm. Services Resources Domain Repositorie s HTTPClient Gateways Persistence
- 8. UNIT TESTS • SolitaryStyle – with mocking • Sociable – no mocking • In very small microservices, Component testing might replace Unit testing entirely • Unit tests are never enough Services Resources Domain Repositorie s HTTPClient Gateways Persistence
- 9. INTEGRATION TESTS • Target:Communication Interfaces • Benefits: Focus • Use Cases: • Security • Fault tolerance • ORM Mapping Services Resources Domain Repositorie s HTTPClient Gateways Persistence Other Microservice DB Client
- 10. INTEGRATION TESTS • Testagainst real dependencies, avoid mocks • Consider separating from main CI pipeline to mitigate fragility Services Resources Domain Repositorie s HTTPClient Gateways Persistence Other Microservice DB Client
- 11. COMPONENT TESTS • Target:A microservice as a whole • Benefits: Comprehensive and fast • Use Cases: • Fast Feedback • Correctness Services Resources Domain Repositorie s HTTPClient Gateways Persistence
- 12.
- 13.
- 14. END TO END •Target: Entire system • Benefits: • Highest level of certainty • Use Cases: • Business critical paths Front End External Service
- 15. END TO END •Mock Nothing!* • Write as few as possible • Time Budgeting * External dependencies that are unstable can be mocked if all else fails
- 16.
- 17.
- 18.