Why testing APIs matters in Express - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is testing APIs important?

Which of the following is the main reason to test APIs in an Express application?

A To ensure the API endpoints return the correct data and handle errors properly

B To change the API endpoints frequently

C To reduce the size of the API codebase

D To make the API run faster by optimizing code

💡 Hint

Think about what testing helps you verify about your API responses and behavior.

Testing APIs helps confirm that endpoints return expected data and handle errors correctly, ensuring reliability and user trust.

❓ component_behavior

intermediate

What happens if an API endpoint is not tested?

Consider an Express API endpoint that is not tested. What is the most likely outcome when a client sends unexpected data?

A The API will log the error but still return correct data

B The API will automatically fix the data and respond correctly

C The API will reject the request with a clear error every time

D The API may crash or return incorrect responses without warning

💡 Hint

Think about what happens when code is not checked for handling bad inputs.

Without tests, unexpected inputs can cause crashes or wrong responses because the API behavior is not verified for such cases.

❓ state_output

advanced

What is the output of this Express API test code?

Given the following Express API test using a testing library, what will be the test result?

Express

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

app.get('/hello', (req, res) => {
  res.status(200).json({ message: 'Hello World' });
});

describe('GET /hello', () => {
  it('responds with JSON containing message', async () => {
    const response = await request(app).get('/hello');
    expect(response.status).toBe(200);
    expect(response.body.message).toBe('Hello World');
  });
});

A The test fails because the endpoint returns status 404

B The test passes because the endpoint returns status 200 and correct message

C The test fails because the response body does not contain 'message'

D The test throws a runtime error due to missing middleware

💡 Hint

Check the endpoint code and what the test expects.

The endpoint returns status 200 and JSON with message 'Hello World', matching the test expectations, so the test passes.

📝 Syntax

advanced

Identify the syntax error in this Express API test snippet

What is the syntax error in the following Express API test code?

Express

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

describe('GET /users', () => {
  it('should return users list', async () => {
    const response = await request(app).get('/users');
    expect(response.status).toBe(200);
    expect(response.body).toBeInstanceOf(Array);
  });
});

A Missing parentheses after describe function

B Missing await keyword before request(app).get('/users')

C Missing semicolon after the get('/users') call

D Missing closing bracket for the it function

💡 Hint

Look carefully at the line with the get('/users') call.

The line calling get('/users') is missing a semicolon at the end, which can cause syntax errors in some environments.

🔧 Debug

expert

Why does this Express API test fail with a timeout?

Review the following Express API test code. Why does the test fail with a timeout error?

Express

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

app.get('/data', (req, res) => {
  // Missing res.send or res.json call
});

describe('GET /data', () => {
  it('should respond with data', async () => {
    const response = await request(app).get('/data');
    expect(response.status).toBe(200);
  });
});

A The endpoint does not send any response, causing the request to hang and timeout

B The test is missing the done callback to finish the test

C The app is not listening on a port, so the request fails

D The test expects status 200 but the endpoint returns 404

💡 Hint

Check what the endpoint does when it receives a request.

The endpoint handler does not send any response, so the client waits forever and the test times out.