Microservices Testing Strategies for Microservices 2

Question 1

Which type of test is most effective for detecting issues that only appear when multiple microservices interact together in a realistic environment?

Accepted Answer

End-to-end tests

Answer

End-to-end tests exercise the full system across multiple services, catching integration issues that unit and contract tests cannot reveal since they only emerge from real service interactions.

Question 2

What is the main drawback of relying heavily on end-to-end tests in a microservices architecture?

Accepted Answer

They are slow, brittle, and difficult to maintain as the number of services grows

Answer

End-to-end tests in microservices are notoriously slow and flaky because they depend on the availability and correct behavior of many services simultaneously, making them expensive to maintain.

Question 3

What does 'consumer-driven contract testing' mean?

Accepted Answer

The consumer defines the expected interactions, and the provider verifies it can fulfill them

Answer

In consumer-driven contract testing, the consumer records the interactions it expects, and the provider's test suite verifies it satisfies all consumer contracts, giving consumers control over the interface.

Question 4

In microservices testing, what is a 'stub'?

Accepted Answer

A lightweight replacement that returns predefined responses without complex logic

Answer

A stub is a simple test double that returns hardcoded or predefined responses to specific inputs, allowing the service under test to behave as if a real dependency responded.

Question 5

Which tool is commonly used to record and replay HTTP interactions between microservices for testing purposes?

Accepted Answer

WireMock

Answer

WireMock is a popular HTTP mock server that can record real service interactions and replay them during tests, enabling isolated testing without live dependencies.

Microservices Practice Test

Microservices Practice Test

Microservices Testing Strategies for Microservices 2