Integration testing patterns in Node.js - Performance & Optimization

Performance: Integration testing patterns

MEDIUM IMPACT

Integration testing patterns affect the speed of test execution and resource usage during development, impacting developer feedback loops and CI pipeline efficiency.

Running integration tests that involve database and external service calls

Node.js

import { setupTestDB, teardownTestDB } from './testUtils';
import nock from 'nock';

describe('User API', () => {
  beforeAll(async () => await setupTestDB());
  afterAll(async () => await teardownTestDB());

  beforeEach(() => {
    nock('http://real-api.com')
      .post('/users')
      .reply(201, { id: 1, name: 'Alice' });
  });

  it('creates a user', async () => {
    const response = await fetch('http://real-api.com/users', { method: 'POST', body: JSON.stringify({name: 'Alice'}) });
    expect(response.status).toBe(201);
  });
});

Mocks external calls and reuses a test database connection, reducing network delays and setup overhead.

📈 Performance Gainreduces test runtime by 70%+; stable and fast CI; lower resource consumption

Running integration tests that involve database and external service calls

Node.js

describe('User API', () => {
  it('creates a user', async () => {
    await db.connect();
    await db.clear();
    const response = await fetch('http://real-api.com/users', { method: 'POST', body: JSON.stringify({name: 'Alice'}) });
    expect(response.status).toBe(201);
    await db.disconnect();
  });
});

Tests connect to real external services and databases for each test, causing slow execution and flaky tests due to network or state issues.

📉 Performance Costblocks test suite for seconds per test; high resource usage; unreliable CI runs

Performance Comparison

Pattern	Network Calls	Resource Usage	Test Runtime	Verdict
Real external calls per test	Multiple real HTTP requests	High (DB connect/disconnect each test)	Slow (seconds per test)	[X] Bad
Mocked external calls with shared DB setup	Mocked HTTP requests	Low (shared DB connection)	Fast (milliseconds per test)	[OK] Good

Rendering Pipeline

Integration testing patterns do not affect browser rendering but influence the development environment's resource usage and test execution speed.

→Test Execution

→Network Calls

→Resource Allocation

⚠️ BottleneckNetwork calls and database setup/teardown during tests

Optimization Tips

1Avoid real network calls in integration tests to reduce flakiness and slowdowns.

2Mock external services to speed up test execution and lower resource use.

3Reuse database connections and setup to minimize overhead during tests.

Performance Quiz - 3 Questions

What is a main performance drawback of integration tests that hit real external APIs every run?

A They cause slow and flaky tests due to network delays and variability

B They reduce bundle size of the application

C They improve user experience by testing real data

D They speed up test execution by avoiding mocks

DevTools: Node.js Profiler or CI logs

How to check: Run tests with profiling enabled or verbose logging; measure time spent on network calls and DB setup per test

What to look for: Long delays in network or DB setup indicate slow integration test patterns; fast tests show minimal external calls and reused resources

Practice

1. What is the main goal of integration testing in a Node.js application?

easy

A. To check the syntax of the code

B. To test individual functions in isolation

C. To verify that different parts of the app work together correctly

D. To measure the app's performance under load

Solution

1. Step 1: Understand integration testing purpose

   Integration testing focuses on checking if multiple parts of the app interact correctly, not just individual pieces.

2. Step 2: Compare with other testing types

   Syntax checking is done by linters, unit tests check single functions, and performance tests measure speed, so these are not integration tests.

3. Final Answer:

   To verify that different parts of the app work together correctly -> Option C

4. Quick Check:

   Integration testing = check parts working together [OK]

Hint: Integration tests check combined parts, not single functions [OK]

Common Mistakes:

• Confusing integration tests with unit tests
• Thinking integration tests check code syntax
• Mixing integration tests with performance testing

2. Which of the following is the correct way to define a setup hook in a Node.js integration test using Mocha?

easy

A. init(() => { /* setup code */ })

B. setup(() => { /* setup code */ })

C. start(() => { /* setup code */ })

D. beforeEach(() => { /* setup code */ })

Solution

1. Step 1: Recall Mocha setup hooks

   Mocha uses beforeEach and before hooks to run setup code before tests.

2. Step 2: Identify correct syntax

   Only beforeEach is a valid Mocha hook; setup, init, and start are not Mocha functions.

3. Final Answer:

   beforeEach(() => { /* setup code */ }) -> Option D

4. Quick Check:

   Mocha setup hook = beforeEach [OK]

Hint: Mocha uses beforeEach for setup, not setup or init [OK]

Common Mistakes:

• Using non-existent hook names like setup or init
• Confusing beforeEach with afterEach
• Forgetting arrow function syntax

3. Consider this Node.js integration test snippet using Jest and Supertest:

test('GET /users returns 200', async () => {
  const response = await request(app).get('/users');
  expect(response.statusCode).toBe(200);
});

What does this test check?

medium

A. That the /users endpoint returns a JSON array

B. That the /users endpoint returns a 200 status code

C. That the app throws an error on /users

D. That the /users endpoint is unreachable

Solution

1. Step 1: Analyze the test code

   The test sends a GET request to '/users' and checks the response status code.

2. Step 2: Understand the assertion

   The assertion expects the status code to be 200, meaning success.

3. Final Answer:

   That the /users endpoint returns a 200 status code -> Option B

4. Quick Check:

   Response status 200 means success [OK]

Hint: Check what the expect() function tests in the code [OK]

Common Mistakes:

• Assuming it checks response body instead of status
• Thinking it tests error or unreachable endpoint
• Ignoring async/await usage

4. You wrote this integration test using Jest:

beforeAll(() => {
  db.connect();
});

test('fetch data', async () => {
  const data = await db.getData();
  expect(data).toBeDefined();
});

afterAll(() => {
  db.disconnect();
});

But the test fails because the database connection is not ready. What is the likely problem?

medium

A. beforeAll should be async and await db.connect()

B. afterAll should run before the test

C. db.getData() should not be awaited

D. expect(data).toBeDefined() is incorrect syntax

Solution

1. Step 1: Check async setup in beforeAll

   Database connection is asynchronous, so beforeAll must be async and await db.connect() to ensure readiness.

2. Step 2: Verify other parts

   afterAll runs after tests, awaiting db.getData() is correct, and expect syntax is valid.

3. Final Answer:

   beforeAll should be async and await db.connect() -> Option A

4. Quick Check:

   Async setup needs await in beforeAll [OK]

Hint: Async setup needs await in beforeAll hook [OK]

Common Mistakes:

• Not making beforeAll async for async setup
• Misplacing afterAll before tests
• Ignoring await on async calls

5. You want to write an integration test for a Node.js app that creates a user via POST /users and then fetches it via GET /users/:id. Which pattern best ensures your test is reliable and isolated?

hard

A. Use setup hook to create a test user, then test GET /users/:id, and cleanup hook to delete the user

B. Run both POST and GET requests in the same test without cleanup

C. Only test GET /users/:id assuming user exists in database

D. Manually add user in database before tests and never delete

Solution

1. Step 1: Understand test isolation

   Tests should not depend on external data; setup creates needed data, cleanup removes it.

2. Step 2: Apply setup and cleanup hooks

   Creating a user in setup, testing GET, then deleting user in cleanup keeps tests reliable and repeatable.

3. Final Answer:

   Use setup hook to create a test user, then test GET /users/:id, and cleanup hook to delete the user -> Option A

4. Quick Check:

   Setup and cleanup keep tests isolated and reliable [OK]

Hint: Setup and cleanup hooks keep tests clean and repeatable [OK]

Common Mistakes:

• Not cleaning up test data causing flaky tests
• Assuming data exists without setup
• Combining unrelated tests without isolation