POSTMAN REST API EXAMPLE UPDATE
POSTMAN REST API EXAMPLE REGISTRATION
POSTMAN REST API EXAMPLE CODE
POSTMAN REST API EXAMPLE PASSWORD
POSTMAN REST API EXAMPLE DOWNLOAD

This name also appears on the left side of the Collection menu. Structure of an HTTP requestįirst, we should give our request a name to quickly recognize it (“Login” in this case). I have marked the most important settings in red. We can then create any number of requests per collection. Also, you can then run the tests for all the requests in it with a single click. This is like a folder in which you can organize your individual requests. You should create a separate collection for each project/Rest API. If you have installed Postman, this interface awaits you.

Now that we have selected the test cases, we start entering the tests into Postman, structuring them and, of course, testing them. Once you have done this properly, you will save a lot of time in the future. This is more important than running the tests. I hope that I can sensitize you a little with this example. The aim is to look at the request from a different angle in order to cover all marginal cases as far as possible.

Was a valid token for the double opt-in created and successfully stored in the database?.

if VARCHAR is limited to 255 characters)?

Is the username not too long for the database field (e.g.

Are the correct HTTP status codes returned in case of errors?.

Could the database query be executed without errors?.

POSTMAN REST API EXAMPLE PASSWORD

Do the password and password repetition match?.This is all correct, however, we have forgotten some. Does the username already exist in the database?.Were all parameters (user name, password, password repetition) passed?.With a little logical thinking, the following test cases come to mind first:

POSTMAN REST API EXAMPLE REGISTRATION

The user should receive an email to complete the registration ( double opt-in).

Username, password and password repetition are to be queried.

We want to create a function to register a user (/sign-up).

To explain this better, I have created the following requirements as an example: As already mentioned, we have to look especially at the edge cases. You now have to select the appropriate test cases for your app.

401 (Unauthorized) – Example: User has no permission for a URLĪ detailed list of important HTTP status codes can be found here.

400 (Bad Request) – Example: Missing parameters when calling.

201 (Created) – Example: New user was created in the database.

200 (OK) – Example: Request was executed without problems.

POSTMAN REST API EXAMPLE CODE

Another example: If a user requests a URL for which he has no permissions because he is not authorized (not logged in), your Rest API should also return the status code 401 (Unauthorized) with a corresponding error message. You should already return these status codes in the correct use case when developing your Rest API, which will also make testing easier. This is the server’s way of saying that everything is OK. This returns the status of the requested operation. HTTP Status Codesįor each HTTP request, the server responds with an HTTP response, which always contains an HTTP status code.

I explain how this can look in my tutorial on creating a Rest API for a login system. When developing the Rest API, you should already make sure that you select the right method for each route.

DELETE: To delete an entity on the serverĪ complete list of all HTTP request methods can be found here.

POSTMAN REST API EXAMPLE UPDATE

PUT: To create or update an entity on the server.

POST: To send information to the server, which then creates a new user in the database, for example.

GET: To retrieve information from the server, e.g.

These are the four most important of a Rest API: The individual URLs of a Rest API (routes in programming) all have a specific HTTP request method. Before that, however, we need to clarify two basic concepts: Advertisements 1.1. Edge cases are test inputs that are most likely to cause erroneous output or even a program error. We need to think particularly carefully about edge cases. This requires a bit of brain power and also a bit of practice – but is extremely important so that we uncover all potential bugs. Selection of the optimal test casesīefore we enter the requests into Postman and start testing, the first step is to select the test cases. Every time you call a URL in the browser, at least one HTTP request to the server happens in the background. Just to reiterate what a Rest API actually is: A Rest API is the interface between client and server, which can request and send data via simple HTTP requests. If you want to know more about it, feel free to go through my Node.js beginner’s guide. Rest APIs can be developed well with the help of Node.js.

POSTMAN REST API EXAMPLE DOWNLOAD

You can download Postman here (available for Windows, Mac & Linux). I’m only referring to the free version here. If you are working with several people on a shared Rest API, Postman offers a subscription to make working in a team much easier.

Postman rest api example