Unit testing services in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of unit testing in microservices?

To verify that each individual service component works correctly in isolation, ensuring its logic is correct before integration.

beginner

Why should unit tests avoid calling external services or databases?

Because unit tests should be fast, reliable, and isolated. Calling external services makes tests slower and less predictable.

intermediate

What technique is commonly used to isolate dependencies in unit testing microservices?

Mocking or stubbing dependencies to simulate their behavior without invoking real implementations.

intermediate

How does unit testing contribute to the scalability of microservices?

By catching bugs early in small components, unit testing reduces errors in production and supports easier scaling of individual services.

beginner

What is a good practice for naming unit tests in microservices?

Use descriptive names that clearly state the condition and expected outcome, like 'shouldReturnErrorWhenInputIsInvalid'.

What is the primary focus of unit testing in microservices?

A Testing user interface responsiveness

B Testing the entire system end-to-end

C Testing network latency between services

D Testing individual service components in isolation

Unit testing focuses on verifying small parts of the system independently, not the whole system or network.

Which of the following is NOT a reason to mock dependencies in unit tests?

A To test real database performance

B To speed up test execution

C To isolate the unit under test

D To avoid flaky tests caused by external services

Unit tests should not test real database performance; that is for integration or performance tests.

What is a sign of a well-written unit test?

A It clearly describes the tested behavior and runs quickly

B It depends on multiple external services

C It runs slowly and intermittently fails

D It tests multiple services at once

Good unit tests are fast, reliable, and clearly describe what they test.

Which tool or technique is commonly used to simulate dependencies in unit tests?

A Profiling

B Load testing

C Mocking

D Logging

Mocking replaces real dependencies with fake ones to isolate the unit under test.

Why is unit testing important before integration testing in microservices?

A It tests the entire system's user interface

B It ensures individual parts work correctly, reducing integration errors

C It measures network bandwidth

D It replaces the need for integration testing

Unit testing verifies components individually, making integration smoother and less error-prone.

Explain how mocking helps in unit testing microservices and why it is important.

Think about how you can test a part without involving others.

Describe best practices for writing effective unit tests for microservices.

Imagine explaining to a friend how to write a good test.

Practice

1. What is the main purpose of unit testing in microservices?

easy

A. To deploy the service automatically

B. To test the entire system end-to-end

C. To monitor service performance in production

D. To test small parts of a service independently

Solution

1. Step 1: Understand unit testing scope

   Unit testing focuses on testing small, isolated parts of a service, not the whole system.

2. Step 2: Differentiate from other testing types

   End-to-end tests check the entire system, while unit tests check individual components.

3. Final Answer:

   To test small parts of a service independently -> Option D

4. Quick Check:

   Unit testing = small parts tested independently [OK]

Hint: Unit tests check small parts, not whole system [OK]

Common Mistakes:

• Confusing unit tests with integration or end-to-end tests
• Thinking unit tests deploy or monitor services
• Believing unit tests require full system setup

2. Which of the following is the correct way to mock a database call in a unit test for a microservice?

easy

A. Replace the database call with a mock object returning fixed data

B. Call the real database and check results

C. Skip the database call and do nothing

D. Use the production database credentials in the test

Solution

1. Step 1: Understand mocking purpose

   Mocks replace real dependencies to isolate the unit under test and control test data.

2. Step 2: Identify correct mocking practice

   Replacing the database call with a mock object returning fixed data allows testing without real DB access.

3. Final Answer:

   Replace the database call with a mock object returning fixed data -> Option A

4. Quick Check:

   Mocking = replace real calls with controlled fake ones [OK]

Hint: Mocks replace real calls with fake data in tests [OK]

Common Mistakes:

• Using real database in unit tests
• Skipping important calls without replacement
• Using production credentials in tests

3. Consider this Python unit test snippet for a microservice method that fetches user data:

def test_get_user_data(mocker):
    mock_db = mocker.patch('service.database.get_user')
    mock_db.return_value = {'id': 1, 'name': 'Alice'}
    result = service.get_user_data(1)
    assert result['name'] == 'Alice'

What will this test verify?

medium

A. That get_user_data returns user name 'Alice' using mocked DB

B. That the real database returns user Alice

C. That the database call is skipped entirely

D. That the service raises an error for user 1

Solution

1. Step 1: Analyze mocking effect

   The database call get_user is replaced by a mock returning fixed user data with name 'Alice'.

2. Step 2: Understand test assertion

   The test checks if get_user_data returns a result with name 'Alice', confirming it uses the mocked data.

3. Final Answer:

   That get_user_data returns user name 'Alice' using mocked DB -> Option A

4. Quick Check:

   Mocked DB returns Alice, test checks service uses it [OK]

Hint: Mock return_value sets test data; assert checks service output [OK]

Common Mistakes:

• Assuming real DB is called
• Thinking database call is skipped without replacement
• Expecting error instead of valid data

4. A developer writes this unit test for a microservice method:

def test_process_order():
    result = process_order(123)
    assert result == 'Success'

But the test fails because process_order calls an external payment service. What is the best fix?

medium

A. Rewrite process_order to not call payment service

B. Add a mock for the external payment service call

C. Run the test only when payment service is available

D. Remove the assertion to avoid failure

Solution

1. Step 1: Identify external dependency issue

   process_order calls an external service, causing test failure due to dependency.

2. Step 2: Apply mocking to isolate test

   Mocking the external payment service call isolates the unit test and avoids real external calls.

3. Final Answer:

   Add a mock for the external payment service call -> Option B

4. Quick Check:

   Mock external calls to isolate unit tests [OK]

Hint: Mock external services to avoid test failures [OK]

Common Mistakes:

• Removing assertions instead of fixing dependencies
• Running tests only when external services are up
• Changing production code to fix tests

5. You want to unit test a microservice method that calls two other services: a user service and an inventory service. Which approach best ensures your unit test is reliable and fast?

hard

A. Skip testing this method because it depends on other services

B. Call both real services during the test to check integration

C. Mock both user and inventory service calls with fixed responses

D. Test only the user service call and ignore inventory service

Solution

1. Step 1: Understand unit test isolation

   Unit tests should isolate the method by mocking external service calls to avoid flakiness and slowness.

2. Step 2: Apply mocks to all external dependencies

   Mocking both user and inventory service calls ensures the test is reliable and fast without real network calls.

3. Final Answer:

   Mock both user and inventory service calls with fixed responses -> Option C

4. Quick Check:

   Mock all external calls for reliable, fast unit tests [OK]

Hint: Mock all external services for isolated unit tests [OK]

Common Mistakes:

• Calling real services in unit tests
• Skipping tests due to dependencies
• Partially mocking dependencies leading to flaky tests