Middleware testing strategies in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is middleware in Express?

Middleware is a function that runs during the request-response cycle. It can modify the request or response objects, end the request, or call the next middleware.

beginner

Why do we test middleware separately in Express apps?

Testing middleware separately helps ensure each piece works correctly on its own before combining them. It isolates logic and catches bugs early.

beginner

Name a common tool used for testing Express middleware.

Supertest is commonly used to test Express middleware by simulating HTTP requests and checking responses.

intermediate

How can you test if middleware calls the next() function properly?

You can mock the next() function and check if it was called during the middleware execution.

intermediate

What is a key strategy to test middleware that modifies the request or response objects?

Create mock request and response objects, run the middleware, then check if the objects were modified as expected.

What does Express middleware typically receive as arguments?

A request, response, finish

B request, response, callback

C req, res, next

D req, res, done

Express middleware functions receive three arguments: req (request), res (response), and next (a function to call the next middleware).

Which tool is best suited for simulating HTTP requests to test middleware?

A Supertest

B Mocha

C Chai

D ESLint

Supertest is designed to simulate HTTP requests and test Express middleware and routes.

How do you verify that middleware correctly ends a response?

A Check if res.end or res.send was called

B Check if next() was called

C Check if req.body exists

D Check if middleware returns true

Middleware that ends a response usually calls res.end or res.send. Testing if these were called confirms response completion.

What is a good way to test error-handling middleware?

A Only test with valid requests

B Pass an error object to next() and check response

C Call middleware without arguments

D Ignore error middleware in tests

Error-handling middleware is triggered by passing an error to next(). Testing this ensures errors are handled properly.

Why mock req and res objects in middleware tests?

A To avoid writing tests

B To speed up database queries

C To test UI components

D To isolate middleware logic without a real server

Mocking req and res lets you test middleware logic alone, without needing a full server or network.

Explain how you would test an Express middleware that adds a property to the request object.

Think about how to simulate the request and check changes.

Describe strategies to test middleware that handles errors in Express.

Focus on how error middleware is triggered and verified.

Practice

1. What is the main purpose of testing middleware in an Express app?

easy

A. To verify that middleware correctly processes requests and responses

B. To check the database connection speed

C. To test the frontend user interface

D. To measure server hardware performance

Solution

1. Step 1: Understand middleware role

   Middleware functions handle requests and responses in Express apps.

2. Step 2: Identify testing focus

   Testing middleware ensures it processes requests and responses correctly.

3. Final Answer:

   To verify that middleware correctly processes requests and responses -> Option A

4. Quick Check:

   Middleware testing = request/response handling [OK]

Hint: Middleware tests check request and response flow [OK]

Common Mistakes:

• Confusing middleware testing with UI testing
• Testing unrelated server hardware
• Ignoring request and response handling

2. Which syntax correctly uses a testing library to simulate a request to Express middleware?

easy

A. request(app).get('/path').expect(200, done)

B. app.request('/path').send(200)

C. middleware.test('/path').status(200)

D. express.test(app).get('/path').check(200)

Solution

1. Step 1: Recognize common testing syntax

   Using 'request(app).get(path).expect(status, done)' is standard with supertest library.

2. Step 2: Compare options

   Only request(app).get('/path').expect(200, done) matches valid syntax for simulating requests in Express tests.

3. Final Answer:

   request(app).get('/path').expect(200, done) -> Option A

4. Quick Check:

   Simulate request = request(app).get() [OK]

Hint: Use request(app).get() to simulate Express requests [OK]

Common Mistakes:

• Using non-existent methods like app.request()
• Confusing middleware with app methods
• Incorrect chaining of test methods

3. Given this middleware test snippet, what will be the output if the middleware calls next() without error?

app.use((req, res, next) => {
  if (req.query.fail) return next(new Error('Fail'));
  res.status(200).send('Success');
});

request(app).get('/?fail=true').expect(500, done);

medium

A. The test passes with status 200

B. The test fails because status 200 is sent

C. The test throws a syntax error

D. The test passes because error triggers 500 status

Solution

1. Step 1: Analyze middleware behavior on fail query

   If req.query.fail is true, middleware calls next() with an error, triggering Express error handling.

2. Step 2: Understand test expectation

   The test expects status 500, which matches Express default error response status.

3. Final Answer:

   The test passes because error triggers 500 status -> Option D

4. Quick Check:

   Error passed to next() = 500 response [OK]

Hint: Error in next() triggers 500 status by default [OK]

Common Mistakes:

• Assuming next() without error sends 200
• Ignoring error passed to next()
• Confusing status codes for errors

4. You wrote this test but it always times out. What is the likely error?

app.use((req, res, next) => {
  if (!req.headers.auth) return res.status(401);
  next();
});

request(app).get('/').expect(401, done);

medium

A. next() is called twice causing conflict

B. Missing res.send() causes response never to finish

C. Incorrect HTTP method used in request

D. Middleware does not check headers properly

Solution

1. Step 1: Check middleware response on missing auth

   res.status(401) sets status but does not end response without res.send() or res.end().

2. Step 2: Understand test timeout cause

   Without ending response, test waits indefinitely causing timeout.

3. Final Answer:

   Missing res.send() causes response never to finish -> Option B

4. Quick Check:

   res.status() alone doesn't end response [OK]

Hint: Always end response with res.send() or res.end() [OK]

Common Mistakes:

• Assuming res.status() ends response
• Calling next() after sending response
• Using wrong HTTP method in test

5. You want to test middleware that conditionally modifies the request object and passes control. Which approach best ensures both modification and flow are tested?

hard

A. Test middleware by calling it without any request data

B. Only check the final response status code

C. Use a mock request object and spy on next() to confirm it was called

D. Skip testing and rely on manual checks

Solution

1. Step 1: Understand middleware modifies request and calls next()

   Testing must confirm request changes and that next() is called to continue flow.

2. Step 2: Choose testing approach

   Using a mock request and spying on next() lets you verify both modification and flow control.

3. Final Answer:

   Use a mock request object and spy on next() to confirm it was called -> Option C

4. Quick Check:

   Mock request + spy next() = full middleware test [OK]

Hint: Spy next() and check request changes for full test [OK]

Common Mistakes:

• Ignoring next() call verification
• Testing only response status
• Not providing request data in tests