Integration vs unit test decision in Express - Quick Revision & Key Differences

Recall & Review

beginner

What is a unit test in Express?

A unit test checks a small part of your Express app, like a single function or middleware, in isolation without involving other parts or external systems.

beginner

What does an integration test do in Express?

An integration test checks how different parts of your Express app work together, like routes, middleware, and database calls, to ensure they cooperate correctly.

intermediate

When should you choose a unit test over an integration test?

Choose a unit test when you want to quickly check a small piece of code without external dependencies, making tests fast and easy to fix if broken.

intermediate

Why are integration tests important in Express apps?

Integration tests catch problems that happen when parts of the app interact, like route handlers calling the database, which unit tests alone might miss.

intermediate

What is a key sign you need an integration test in Express?

If your feature depends on multiple parts working together, like middleware, routes, and database, you need an integration test to check the full flow.

Which test focuses on a single function without external systems?

A Performance test

B Unit test

C End-to-end test

D Integration test

Unit tests isolate one function or module, ignoring external parts.

What does an integration test in Express usually include?

A Multiple parts like routes and database working together

B Only one middleware function

C Just the database queries

D Only front-end UI

Integration tests check how different parts like routes and database interact.

When is a unit test preferred over an integration test?

A When testing the whole app flow

B When testing user interface

C When testing network speed

D When testing a small isolated function

Unit tests are best for small, isolated pieces of code.

Which test type is slower but checks more parts working together?

A Integration test

B Unit test

C Static code analysis

D Linting

Integration tests involve multiple components and take longer to run.

What is a sign you should write an integration test in Express?

A Testing a single helper function

B Testing CSS styles

C Testing route handling with database calls

D Testing a math calculation

Integration tests are needed when routes interact with databases or other services.

Explain the main difference between unit tests and integration tests in Express.

Think about testing one piece vs testing how pieces connect.

Describe a situation in an Express app where you would choose an integration test instead of a unit test.

Consider when parts depend on each other.

Practice

1. Which type of test in Express focuses on checking a single function or module in isolation?

easy

A. Unit test

B. Integration test

C. End-to-end test

D. Performance test

Solution

1. Step 1: Understand test types in Express

   Unit tests focus on small pieces like functions or modules alone, without dependencies.

2. Step 2: Identify test purpose

   Integration tests check how parts work together, so they are not isolated.

3. Final Answer:

   Unit test -> Option A

4. Quick Check:

   Single module check = Unit test [OK]

Hint: Unit tests isolate one part; integration tests combine parts [OK]

Common Mistakes:

• Confusing integration tests with unit tests
• Thinking end-to-end tests are unit tests
• Assuming performance tests check single functions

2. Which of the following is the correct way to write a simple unit test for an Express middleware function?

easy

A. Use a browser to manually check middleware behavior

B. Test the middleware by calling it with mock request and response objects

C. Start the Express server and send HTTP requests to test the middleware

D. Run the entire app and check logs for middleware output

Solution

1. Step 1: Understand unit test scope

   Unit tests isolate the middleware by calling it directly with mock objects, no server needed.

2. Step 2: Identify correct testing method

   Starting the server or manual checks are integration or manual tests, not unit tests.

3. Final Answer:

   Test the middleware by calling it with mock request and response objects -> Option B

4. Quick Check:

   Mock objects for unit test [OK]

Hint: Unit test = call function with mocks, no server start [OK]

Common Mistakes:

• Starting server for unit tests
• Using manual browser checks for unit tests
• Confusing integration test methods with unit tests

3. Consider this Express test snippet:

request(app)
  .get('/users')
  .expect(200)
  .end((err, res) => {
    if (err) throw err;
    console.log(res.body.length);
  });

What type of test is this and what does it check?

medium

A. Unit test; mocks the database call

B. Unit test; checks a single function's return value

C. Integration test; checks the route and middleware working together

D. Performance test; measures response time

Solution

1. Step 1: Analyze the test code

   The test sends an HTTP GET request to '/users' on the app, expecting status 200.

2. Step 2: Identify test type

   This checks the route handler and middleware together, so it's an integration test.

3. Final Answer:

   Integration test; checks the route and middleware working together -> Option C

4. Quick Check:

   HTTP request test = Integration test [OK]

Hint: HTTP request tests check multiple parts together [OK]

Common Mistakes:

• Calling this a unit test
• Assuming it mocks database calls
• Thinking it measures performance

4. You wrote a test that starts the Express server and sends HTTP requests, but it runs very slowly and sometimes fails due to timing issues. What is the best way to fix this problem?

medium

A. Rewrite the test as a unit test using mocks instead of starting the server

B. Add more delays in the test to wait for responses

C. Increase server timeout settings in Express

D. Run the test on a faster machine

Solution

1. Step 1: Identify the problem cause

   Starting the server and sending real HTTP requests makes tests slow and flaky.

2. Step 2: Choose a better testing approach

   Using unit tests with mocks avoids server start and speeds up tests, reducing timing issues.

3. Final Answer:

   Rewrite the test as a unit test using mocks instead of starting the server -> Option A

4. Quick Check:

   Mocks speed tests, avoid server start [OK]

Hint: Mocks speed tests; avoid real server start [OK]

Common Mistakes:

• Adding delays instead of fixing test design
• Changing server settings unnecessarily
• Blaming hardware instead of test approach

5. You want to test an Express app's user login flow. Which approach best balances speed and coverage by combining unit and integration tests?

hard

A. Only write integration tests for the login route to cover everything at once

B. Test manually in the browser without automated tests

C. Write unit tests for the entire Express app without any integration tests

D. Write unit tests for the login function logic and integration tests for the full login route with database

Solution

1. Step 1: Understand testing goals

   Unit tests check small parts fast; integration tests check how parts work together.

2. Step 2: Combine tests for best results

   Writing unit tests for login logic and integration tests for the route with database balances speed and coverage.

3. Final Answer:

   Write unit tests for the login function logic and integration tests for the full login route with database -> Option D

4. Quick Check:

   Combine unit + integration tests for best coverage [OK]

Hint: Use unit tests for logic, integration for routes [OK]

Common Mistakes:

• Relying only on integration tests
• Skipping integration tests entirely
• Ignoring automated tests in favor of manual