Testing authentication flows in Express - Performance & Optimization

Performance: Testing authentication flows

MEDIUM IMPACT

Testing authentication flows affects the development feedback loop and server response time during tests, impacting developer productivity and CI pipeline speed.

Testing user login with real database calls

Express

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

jest.mock('../services/authService');

test('login with mocked auth service', async () => {
  authService.login.mockResolvedValue({ token: 'fake-token' });
  const response = await request(app)
    .post('/login')
    .send({ username: 'user', password: 'pass' });
  expect(response.statusCode).toBe(200);
  expect(response.body.token).toBe('fake-token');
});

Mocks authentication service to avoid real DB calls, making tests faster and more reliable.

📈 Performance GainReduces test time by 70-90%; avoids server load; speeds up CI feedback.

Testing user login with real database calls

Express

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

test('login with real DB', async () => {
  const response = await request(app)
    .post('/login')
    .send({ username: 'user', password: 'pass' });
  expect(response.statusCode).toBe(200);
});

This test hits the real database, causing slow tests and potential flakiness due to external dependencies.

📉 Performance CostBlocks test suite for 100-300ms per test; slows CI pipeline; increases server load during tests.

Performance Comparison

Pattern	Server Calls	Test Duration	Resource Usage	Verdict
Real DB calls in tests	Multiple real DB queries	Slow (100-300ms per test)	High CPU and DB load	[X] Bad
Mocked auth service	No real DB calls	Fast (10-50ms per test)	Low resource usage	[OK] Good
Full server startup	Starts HTTP server	Slow startup (500ms+)	High memory and CPU	[X] Bad
Direct app instance with supertest	No server startup	Fast startup	Low resource usage	[OK] Good

Rendering Pipeline

Testing authentication flows does not directly affect browser rendering but impacts server response time and test execution speed, which indirectly affects developer experience and deployment pipelines.

→Server Response

→Test Execution

⚠️ BottleneckReal database calls and full server startup during tests

Optimization Tips

1Avoid real database calls in authentication tests to speed up test execution.

2Do not start the full server for each test; use app instance with supertest instead.

3Mock external services to reduce resource usage and improve test reliability.

Performance Quiz - 3 Questions

What is the main performance issue when tests hit the real database during authentication flow testing?

A Tests run faster because real data is used

B Tests consume less memory

C Tests become slower and less reliable due to external dependencies

D Tests avoid network latency

DevTools: Performance

How to check: Run tests with Node.js --inspect flag and profile test execution time; alternatively, use test runner's built-in timing reports.

What to look for: Look for long delays caused by database calls or server startup; identify slow tests and optimize mocks.

Practice

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

easy

A. To check if the server can handle large amounts of traffic

B. To verify users can log in and access protected routes correctly

C. To ensure the database schema is optimized

D. To test the styling of the login page

Solution

1. Step 1: Understand authentication flow testing

   Testing authentication flows means checking if users can log in and access parts of the app that require login.

2. Step 2: Identify the main goal

   The main goal is to verify correct login and access control, not performance or styling.

3. Final Answer:

   To verify users can log in and access protected routes correctly -> Option B

4. Quick Check:

   Authentication testing = verify login and access [OK]

Hint: Authentication tests check login and access only [OK]

Common Mistakes:

• Confusing authentication testing with performance testing
• Thinking styling or database optimization is tested here
• Assuming authentication tests check UI design

2. Which of the following is the correct way to import and use supertest for testing an Express app's authentication route?

easy

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

B. const supertest = import('supertest'); const app = require('./app');

C. import request from 'supertest'; import app from './app';

D. import * as request from 'supertest'; const app = require('./app');

Solution

1. Step 1: Identify CommonJS import syntax

   Most Express apps use CommonJS syntax with require, so const request = require('supertest'); is correct.

2. Step 2: Match import style for app

   Similarly, const app = require('./app'); is correct for CommonJS modules.

3. Final Answer:

   const request = require('supertest'); const app = require('./app'); -> Option A

4. Quick Check:

   Use CommonJS require for supertest and app [OK]

Hint: Use CommonJS require syntax for supertest and app [OK]

Common Mistakes:

• Mixing require() with import in CommonJS code
• Using dynamic import incorrectly
• Using namespace import when default import is expected

3. Given this test code snippet, what will be the status code returned when testing a protected route without authentication?

await request(app).get('/dashboard').expect(401);

medium

A. 401 (Unauthorized) - Access denied

B. 200 (OK) - Access granted

C. 404 (Not Found) - Route missing

D. 500 (Server Error) - Internal error

Solution

1. Step 1: Understand protected route behavior

   Protected routes require authentication; without it, the server should deny access.

2. Step 2: Identify correct HTTP status for unauthorized access

   HTTP status 401 means unauthorized access, which fits this case.

3. Final Answer:

   401 (Unauthorized) - Access denied -> Option A

4. Quick Check:

   Unauthenticated access to protected route = 401 [OK]

Hint: 401 means unauthorized access denied [OK]

Common Mistakes:

• Expecting 200 without authentication
• Confusing 401 with 404 or 500
• Assuming route is missing instead of protected

4. You wrote this test to check login failure:

await request(app).post('/login').send({ username: 'user', password: 'wrong' }).expect(401);

But the test fails even when the server returns 200. What is the likely mistake?

medium

A. The test should use GET instead of POST

B. The test is missing async/await keywords

C. The server does not properly check password and returns 200 anyway

D. The test should expect 404 instead of 401

Solution

1. Step 1: Analyze test expectation vs server behavior

   The test expects 401 for wrong password, but server returns 200, so server likely accepts wrong password.

2. Step 2: Identify root cause

   The server probably lacks proper password validation, causing incorrect success response.

3. Final Answer:

   The server does not properly check password and returns 200 anyway -> Option C

4. Quick Check:

   Wrong password but 200 means server validation missing [OK]

Hint: Check server password validation if test expects 401 but gets 200 [OK]

Common Mistakes:

• Assuming test syntax error without checking server logic
• Using wrong HTTP method for login
• Expecting wrong status code for authentication failure

5. You want to test that after a successful login, the user can access a protected route using the received token. Which sequence correctly tests this flow using supertest?

hard

A. Post login with wrong password, then get protected route with token

B. Get protected route first, then post login with token in body

C. Post login without saving token, then get protected route without headers

D. Post login, save token from response, then get protected route with Authorization header set to token

Solution

1. Step 1: Understand authentication token flow

   After login, server returns a token. This token must be sent in Authorization header to access protected routes.

2. Step 2: Identify correct test sequence

   First post login, save token from response, then use token in Authorization header for protected route request.

3. Final Answer:

   Post login, save token from response, then get protected route with Authorization header set to token -> Option D

4. Quick Check:

   Login -> save token -> use token in header for protected route [OK]

Hint: Save token after login, then use it in Authorization header [OK]

Common Mistakes:

• Trying to access protected route before login
• Not sending token in Authorization header
• Using wrong password in login step