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.

Practice

1. What is the main purpose of integration testing in a microservices architecture?

easy

A. To verify that different microservices communicate and work together correctly

B. To test the user interface of a single microservice

C. To check the performance of a single microservice under load

D. To test the database schema independently

Solution

1. Step 1: Understand integration testing role

   Integration testing focuses on checking how different parts of a system interact and work together.

2. Step 2: Apply to microservices context

   In microservices, integration testing ensures that services communicate and exchange data correctly.

3. Final Answer:

   To verify that different microservices communicate and work together correctly -> Option A

4. Quick Check:

   Integration testing = verify communication [OK]

Hint: Integration tests check service communication, not UI or performance [OK]

Common Mistakes:

• Confusing integration testing with UI testing
• Thinking integration tests check only one service
• Mixing integration testing with performance testing

2. Which of the following is the correct way to write a simple integration test for two microservices communicating via HTTP?

easy

A. Call one service's API and verify the response includes data from the other service

B. Test only the database queries inside one service

C. Run unit tests on each microservice separately

D. Check the UI elements of the frontend application

Solution

1. Step 1: Identify integration test action

   Integration tests call APIs to check if services interact and data flows correctly.

2. Step 2: Match with options

   Call one service's API and verify the response includes data from the other service describes calling one service and verifying response includes data from another, which is correct.

3. Final Answer:

   Call one service's API and verify the response includes data from the other service -> Option A

4. Quick Check:

   Integration test = API call + response check [OK]

Hint: Integration test means calling APIs and checking combined data [OK]

Common Mistakes:

• Testing only database queries (unit test scope)
• Running unit tests instead of integration tests
• Focusing on UI elements, not service communication

3. Consider this integration test code snippet for two microservices A and B:

response = serviceA.callEndpoint('/data')
assert 'user' in response
assert response['user']['id'] == 123
assert response['details']['status'] == 'active'

What is the expected outcome if microservice B fails to provide 'details' data?

medium

A. The test will ignore missing 'details' and succeed

B. The test will fail at the assertion checking 'details' key

C. The test will throw a syntax error

D. The test will pass because 'user' data is present

Solution

1. Step 1: Analyze test assertions

   The test checks for 'user' key and its 'id', then checks 'details' key's 'status'.

2. Step 2: Consider missing 'details' data

   If 'details' is missing, accessing response['details']['status'] causes failure or error.

3. Final Answer:

   The test will fail at the assertion checking 'details' key -> Option B

4. Quick Check:

   Missing data causes assertion failure [OK]

Hint: Missing keys cause assertion failures, not silent passes [OK]

Common Mistakes:

• Assuming test passes if some keys exist
• Confusing assertion failure with syntax error
• Thinking missing keys are ignored

4. You wrote an integration test that calls microservice A, which calls microservice B internally. The test fails intermittently with timeout errors. What is the most likely cause?

medium

A. The test code has syntax errors

B. Microservice A does not call microservice B at all

C. Microservice B is slow or unresponsive causing timeouts

D. The database schema is incorrect

Solution

1. Step 1: Understand timeout errors in integration tests

   Timeouts usually happen when a service does not respond in expected time.

2. Step 2: Analyze microservice call chain

   Since microservice A calls B internally, if B is slow or down, A's response delays causing timeout.

3. Final Answer:

   Microservice B is slow or unresponsive causing timeouts -> Option C

4. Quick Check:

   Timeout = slow/unresponsive downstream service [OK]

Hint: Timeouts usually mean slow or down called service [OK]

Common Mistakes:

• Blaming syntax errors for runtime timeouts
• Assuming no call happens without checking logs
• Confusing database issues with service timeouts

5. You want to design an automated integration test suite for a microservices system with 5 services communicating via REST APIs. Which approach best ensures reliable and scalable integration testing?

hard

A. Manually test service interactions without automation

B. Use test doubles (mocks) for all services to isolate each test

C. Test only one service at a time with unit tests

D. Deploy all services in a test environment and run end-to-end tests covering real API calls

Solution

1. Step 1: Consider integration testing goals

   Integration tests verify real communication between services, so mocks reduce test coverage.

2. Step 2: Evaluate options for reliability and scalability

   Deploying all services in a test environment and running automated end-to-end tests ensures real interactions and catches integration issues.

3. Final Answer:

   Deploy all services in a test environment and run end-to-end tests covering real API calls -> Option D

4. Quick Check:

   Real environment + automation = reliable integration tests [OK]

Hint: Run real services in test environment for true integration tests [OK]

Common Mistakes:

• Relying only on mocks, missing real integration bugs
• Skipping automation reduces test reliability
• Confusing unit tests with integration tests