Integration vs unit test decision in Express

Introduction

Testing helps find bugs early. Unit tests check small parts alone. Integration tests check parts working together.

When you want to check if a single function or route works correctly by itself.

When you want to verify that multiple parts like routes, database, and middleware work together.

When you fix a bug in one function and want to quickly confirm it works.

When you add a new feature that involves several parts interacting.

When you want to catch errors caused by how parts connect, not just inside one part.

Syntax

Express

Unit test example:
describe('functionName', () => {
  it('does something', () => {
    // test code here
  });
});

Integration test example:
describe('API route', () => {
  it('responds with data', async () => {
    // test code here
  });
});

Unit tests focus on one small piece, like a single function or module.

Integration tests check how multiple parts work together, like routes and database.

Examples

This is an integration test checking the /users route returns a list.

Express

const request = require('supertest');
const app = require('./app');

describe('GET /users', () => {
  it('returns list of users', async () => {
    const response = await request(app).get('/users');
    expect(response.status).toBe(200);
    expect(Array.isArray(response.body)).toBe(true);
  });
});

This is a unit test checking the sum function adds numbers correctly.

Express

const { sum } = require('./math');

describe('sum function', () => {
  it('adds two numbers', () => {
    expect(sum(2, 3)).toBe(5);
  });
});

Sample Program

This example shows both a unit test for a simple function and an integration test for an Express route using that function.

Express

const express = require('express');
const request = require('supertest');

// Simple function to test
function greet(name) {
  return `Hello, ${name}!`;
}

// Express app with one route
const app = express();
app.get('/greet/:name', (req, res) => {
  res.send({ message: greet(req.params.name) });
});

// Unit test for greet function
describe('greet function', () => {
  it('returns greeting message', () => {
    expect(greet('Alice')).toBe('Hello, Alice!');
  });
});

// Integration test for /greet/:name route
describe('GET /greet/:name', () => {
  it('responds with greeting message', async () => {
    const response = await request(app).get('/greet/Bob');
    expect(response.status).toBe(200);
    expect(response.body).toEqual({ message: 'Hello, Bob!' });
  });
});

Important Notes

Unit tests run fast and help find bugs in small parts.

Integration tests take longer but catch problems in how parts work together.

Use both types to keep your app reliable and easier to fix.

Summary

Unit tests check one small piece alone.

Integration tests check multiple parts working together.

Choose unit tests for quick checks, integration tests for full flow checks.

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