Mocking database calls in Express - Step-by-Step Execution

Concept Flow - Mocking database calls

Start Express app

↓

Receive API request

↓

Call database function

↓

Mock intercepts call

↓

Return fake data

↓

Send response with fake data

↓

End request

This flow shows how an Express app receives a request, calls a database function, but the call is intercepted by a mock that returns fake data instead of real database results.

Execution Sample

Express

const express = require('express');
const app = express();

// Mock database function
const db = { getUser: () => ({ id: 1, name: 'Mock User' }) };

app.get('/user', (req, res) => {
  const user = db.getUser();
  res.json(user);
});

This code sets up an Express route that returns a mocked user object instead of calling a real database.

Execution Table

Step	Action	Function Called	Return Value	Response Sent
1	Receive GET /user request	N/A	N/A	N/A
2	Call db.getUser()	db.getUser()	{ id: 1, name: 'Mock User' }	N/A
3	Send JSON response	N/A	N/A	{ id: 1, name: 'Mock User' }
4	Request ends	N/A	N/A	N/A

💡 Request ends after sending mocked user data as JSON response

Variable Tracker

Variable	Start	After Step 2	Final
user	undefined	{ id: 1, name: 'Mock User' }	{ id: 1, name: 'Mock User' }

Key Moments - 2 Insights

Why does the app return a user object without connecting to a real database?

Because the db.getUser function is mocked to return a fixed object, as shown in execution_table step 2, so no real database call happens.

What happens if we remove the mock and call a real database function?

The app would try to connect to the database, which might delay response or fail if the database is unavailable. The mock avoids this by returning data immediately.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'user' after step 2?

A undefined

B { id: 1, name: 'Mock User' }

C null

D {}

💡 Hint

Check the variable_tracker table under 'After Step 2' for 'user'

At which step is the JSON response sent back to the client?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Response Sent' column in execution_table

If the mock was removed, what would change in the execution flow?

A The response would be sent before calling db.getUser

B The app would not receive the request

C db.getUser would call the real database instead of returning fake data

D The mock would still intercept the call

💡 Hint

Refer to key_moments about what happens without the mock

Concept Snapshot

Mocking database calls in Express:
- Replace real DB functions with fake ones returning fixed data
- Allows testing API routes without real DB
- Mocked functions return immediately
- Helps isolate backend logic from DB
- Use mocks during development and testing

Full Transcript

This example shows how an Express app handles a GET request to /user by calling a mocked database function. Instead of querying a real database, the mock returns a fixed user object immediately. The app then sends this mocked data as a JSON response. This approach helps developers test and develop APIs without needing a real database connection. The execution table traces each step: receiving the request, calling the mock, returning fake data, and sending the response. The variable tracker shows the user variable getting assigned the mocked data. Key moments clarify why mocking avoids real database calls and what changes if the mock is removed. The quiz tests understanding of the flow and variable states.