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

Unit tests

Answer

Contract tests

Answer

Property-based tests

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

They cannot find bugs that unit tests miss

Answer

They require contract files to be shared between teams

Answer

They cannot be automated and require manual execution

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

The service provider defines the contract and consumers must adapt to it

Answer

An external team writes contracts for all services

Answer

Contracts are auto-generated from OpenAPI specs

Question 4

In microservices testing, what is a 'stub'?

Accepted Answer

A lightweight replacement that returns predefined responses without complex logic

Answer

A real service deployed in a test environment

Answer

A tool that records and replays HTTP interactions

Answer

A performance benchmark baseline

Question 5

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

Accepted Answer

WireMock

Answer

JUnit

Answer

Prometheus

Answer

Kafka

Question 6

What is 'mutation testing' and why is it used in microservices development?

Accepted Answer

Automatically introducing small code changes to verify that existing tests detect them

Answer

Testing how services handle schema changes between versions

Answer

Testing how microservices adapt when dependencies change their APIs

Answer

Generating tests by mutating existing test cases

Question 7

What is the purpose of a 'smoke test' in a microservices deployment pipeline?

Accepted Answer

Run a minimal set of critical tests immediately after deployment to verify basic functionality

Answer

Test service performance under heavy load

Answer

Detect memory leaks in services over time

Answer

Validate all edge cases and error paths