API Testing

This lesson covers API Testing. Here is the idea in simple words, then we write real code.

What you will learn

• What api testing means — in normal words, not textbook words
• How it works step by step
• Code you can run today on your laptop
• Where teams use this in real projects

Before you start

• Software: Node.js LTS from nodejs.org, VS Code, and a terminal
• Knowledge: Earlier lessons in this Node.js course
• Previous lesson: Supertest — Complete Guide

Explain it simply

API testing checks every endpoint — happy path, validation errors, auth failures — automatically in CI.

Why developers use this

• Shipping is a core skill
• Automate tests and deploy
• Portfolio needs a live URL

How it works (step by step)

1. Tests pass on your machine.
2. Build a Docker image or set Node version on the host.
3. Set environment variables on the server (never commit secrets).
4. Hit the health URL and watch logs for the first real users.

Code example — type this yourself

describe('POST /api/tasks', () => {
  it('creates a task', async () => {
    const res = await request(app).post('/api/tasks').send({ title: 'Test' });
    expect(res.status).toBe(201);
  });
});

Run tests on every git push with GitHub Actions.

What each part does

• describe('POST /api/tasks', () => { — Line 1: runs as written.
• it('creates a task', async () => { — Async work — Node can serve other users while this waits.
• const res = await request(app).post('/api/tasks').send({ title: 'Test' }); — Async work — Node can serve other users while this waits.
• expect(res.status).toBe(201); — Line 4: runs as written.
• }); — Line 5: runs as written.
• }); — Line 6: runs as written.

Real life: where API Testing shows up

After tests pass locally, the team uses API Testing to ship the same build to staging, then production, with the same Node version everywhere. In interviews, explain the trade-off you chose and what you would measure in production.

Try it yourself — hands-on

1. Create a new file (e.g. api-testing-demo.js) in an empty folder
2. Type the example code for API Testing yourself — typing helps memory
3. Run node on that file and read the output
4. Change one line (a value, a message, a route path) and run again to see what breaks or improves

Common mistakes (avoid these)

• Skipping the terminal — API Testing only feels easy after you run code yourself.

Interview note

Senior interviews may ask how API Testing behaves under load, failure, or security review — mention logging, timeouts, and validation.

Summary

• You can explain API Testing in your own words
• You ran working code — not just read about it
• You know one mistake to avoid and one real place teams use this