Integration testing in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Integration Testing Scope in Microservices

Which of the following best describes the primary focus of integration testing in a microservices architecture?

A Testing the interactions and data flow between multiple microservices and their dependencies

B Testing individual microservices in isolation without external dependencies

C Testing the user interface and user experience of the application

D Testing the deployment scripts and infrastructure automation

💡 Hint

Think about how microservices communicate and what integration testing aims to verify.

Integration testing in microservices focuses on verifying that different services work together correctly, including their communication and data exchange.

❓ Architecture

intermediate

Designing an Integration Test Environment for Microservices

You need to design an integration test environment for a microservices system. Which approach ensures the environment is closest to production while allowing isolated testing?

A Use mocks and stubs for all external services and databases

B Run integration tests on the developer's local machine with partial services running

C Deploy all microservices and their real dependencies in a dedicated test environment with isolated databases

D Test only one microservice at a time with its dependencies mocked

💡 Hint

Consider the importance of realistic interactions and data consistency in integration tests.

Deploying all microservices and real dependencies in an isolated environment simulates production closely, enabling reliable integration testing.

❓ scaling

advanced

Scaling Integration Tests for a Growing Microservices System

As the number of microservices grows, integration tests become slower and harder to maintain. Which strategy best helps scale integration testing effectively?

A Manually test critical service interactions instead of automated integration tests

B Run all integration tests sequentially on a single test server

C Skip integration tests and rely only on unit tests for each microservice

D Use test parallelization with service virtualization to run tests concurrently and reduce dependencies

💡 Hint

Think about how to reduce test time and dependency complexity while maintaining coverage.

Parallelizing tests and using service virtualization reduces test runtime and dependency issues, enabling scalable integration testing.

❓ tradeoff

advanced

Tradeoffs Between Integration Testing and End-to-End Testing

Which statement best describes a key tradeoff between integration testing and end-to-end testing in microservices?

A End-to-end tests are easier to maintain than integration tests because they test fewer components

B Integration tests are faster and more focused on service communication, while end-to-end tests cover complete user scenarios but are slower and more brittle

C Integration tests cover full user workflows, while end-to-end tests focus on service interactions

D Integration tests do not require any test data setup, unlike end-to-end tests

💡 Hint

Consider test scope, speed, and maintenance effort differences.

Integration tests focus on service interactions and run faster, while end-to-end tests cover full workflows but tend to be slower and more fragile.

❓ estimation

expert

Estimating Integration Test Capacity for a Microservices Platform

You have 50 microservices, each with an average of 10 integration tests. Each test takes 3 minutes to run. You want to run all integration tests daily within 2 hours. How many parallel test runners do you need at minimum?

A 13 parallel test runners

B 50 parallel test runners

C 25 parallel test runners

D 10 parallel test runners

💡 Hint

Calculate total test time and divide by allowed time, then round up.

Total tests = 50 * 10 = 500 tests. Total time serially = 500 * 180s = 90,000s. Allowed time = 2 hours = 7200s. Required runners = ceil(90,000 / 7200) = ceil(12.5) = 13 runners.