Test database setup and teardown in Express - Step-by-Step Execution

Concept Flow - Test database setup and teardown

Start Test Suite

↓

Setup Test DB Connection

↓

Run Tests

↓

Teardown Test DB Connection

↓

End Test Suite

This flow shows how a test database connection is opened before tests run and closed after all tests finish.

Execution Sample

Express

beforeAll(async () => {
  await connectTestDB();
});

afterAll(async () => {
  await disconnectTestDB();
});

This code connects to the test database before tests and disconnects after all tests complete.

Execution Table

Step	Action	Async Operation	State Before	State After	Notes
1	Start test suite	No	DB disconnected	DB disconnected	Test runner starts
2	Run beforeAll hook	connectTestDB()	DB disconnected	DB connected	Test DB connection established
3	Run tests	No	DB connected	DB connected	Tests use DB connection
4	Run afterAll hook	disconnectTestDB()	DB connected	DB disconnected	Test DB connection closed
5	End test suite	No	DB disconnected	DB disconnected	All tests finished

💡 Test suite ends after afterAll hook disconnects the test database.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
DB Connection State	disconnected	connected	connected	disconnected	disconnected

Key Moments - 3 Insights

Why do we connect to the test database before running tests?

Because tests need a live database connection to run queries, as shown in step 2 of the execution_table.

Why must we disconnect the test database after all tests?

To free resources and avoid open connections, as shown in step 4 where disconnectTestDB() is called.

What happens if we forget to disconnect the test database?

The test suite may hang or leak resources because the DB connection stays open, breaking the clean exit shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the DB connection state after step 2?

A disconnected

B connecting

C connected

D disconnecting

💡 Hint

Check the 'State After' column for step 2 in the execution_table.

At which step does the test database connection close?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look for disconnectTestDB() in the 'Async Operation' column in the execution_table.

If we remove the afterAll hook, what will happen to the DB connection state at the end?

A It disconnects automatically

B It stays connected

C It reconnects

D It closes before tests

💡 Hint

Refer to variable_tracker and step 4 in execution_table where disconnectTestDB() is called.

Concept Snapshot

Test DB setup and teardown in Express tests:
- Use beforeAll() to connect test DB before tests
- Use afterAll() to disconnect test DB after tests
- Ensures tests run with DB access
- Prevents resource leaks by closing connection
- Keeps test suite clean and reliable

Full Transcript

This visual execution shows how to set up and tear down a test database connection in Express tests. First, beforeAll hook runs and connects to the test database, changing the DB connection state from disconnected to connected. Then tests run using this connection. After all tests finish, afterAll hook disconnects the test database, returning the connection state to disconnected. This ensures tests have a live DB connection and that resources are freed after tests. Forgetting to disconnect can cause the test suite to hang or leak resources. The execution table tracks each step, showing actions, async operations, and connection states. The variable tracker highlights how the DB connection state changes over time. This pattern keeps tests reliable and clean.