DEV Community

Cover image for Your First API Test in 5 Minutes (No Code Needed)
Nikoela Koleva
Nikoela Koleva

Posted on

Your First API Test in 5 Minutes (No Code Needed)

#beginners #career #testing #api

I'm a student moving into QA, and the first thing that confused me was API testing. It sounds scary. It isn't.

Think of an API as a waiter. You (the client) tell the waiter what you want, the waiter goes to the kitchen (the server) and brings back the answer. Testing an API means checking that the waiter brings the right dish.

You can try it right now. No installs, no code.

Test 1: Ask for something that exists

Open this address in your browser:

https://jsonplaceholder.typicode.com/users/1
Enter fullscreen mode Exit fullscreen mode

JSONPlaceholder is a free fake API made for practice. You should see a user with an id, a name, a username and an email.

What to check:

  • Is the id really 1?
  • Are all the expected fields there?
  • Does the email look like an email?

Test 2: Ask for something that doesn't exist

Now try:

https://jsonplaceholder.typicode.com/users/999999
Enter fullscreen mode Exit fullscreen mode

There is no user 999999, so you should get a "not found" result (status 404 and an empty response). A good API says "no" politely instead of crashing.

Test 3: Don't trust the status code alone

A "200 OK" only means the waiter answered. It doesn't mean the dish is right. Always check the body too: the right fields, the right values, the right data types.

A small trap

If you open the Network tab in your browser, you might see 304 instead of 200 and think something is broken. It isn't. 304 means "Not Modified": the browser reused a saved copy. Tick Disable cache, reload, and you'll see the 200.

Write down what you really see

The golden rule of testing: record the actual result, not the one you expect. If the public API behaves differently from a tutorial, write that down. That's how real testers work.

Want to go further?

I turned what I'm learning into a beginner starter kit: a workbook, a bug report template, an Excel test tracker with 15 ready test cases, API exercises with an answer key, and a guided portfolio project. It's educational (not a certification or a job guarantee), but it gives beginners something concrete to practise and to talk about in interviews.

You can find it here: https://kolevana2.gumroad.com/l/dermjw

What was the first thing that confused you in testing? Tell me in the comments.

Top comments (0)