Test runner – API testing

API testing

Test runner – According to the previous post, you already know how to create simple tests for each API, but a project has too many APIs and too many different tasks, each task is a collection of several APIs how must be solved. Along with that is the management method that you think is applicable to Postman or not? And how to run the test with the least effort.

Test Suites Management

In Postman manage APIs in the form of Collections and depending on the project you will have different management methods. Because the project is released once a week, this is how I manage it.

The problem is, how will I arrange each small task ?

In the previous post, I have guided with a single API with 2 corresponding test types:

1. Syntax Testing (Validation)

2. Functional Testing

According to suggestions from Postman Bloggers, you should not only use 1 request for all your tests, but for each case you will create 1 request, only the Description and Test are different. So this is how I structure the API for each task.

On Postman, it will look like this:

The APIs in Figures 1 to 5 will have different Description and Test sections.



Similarly you will do the same with other cases.

Run Test Suites by Test runner

From the beginning of the series until now, you know how to test the API “manually”, press SEND to check each API. Postman provides the ability to run List API by Folder using the Runner feature.

The Runner screen will appear, here you will be interested in the following components.

1. Folder will run.

2. Environment by project

3. Number of repetitions

4. Option for you to review the Log of the requests you want.

After the run is complete, you will see the following report:

Note: The number of Pass or Fail is calculated on the number of Tests you write, not on the number of Requests you run.

You can see the short version of the report in Summary and save the Log in Export Result.

If you want to see details of each request’s parameters, click on the name of that Request.

So that’s done with the Runner part, a feature that Postman supports Automated Testing. If you have any questions, leave a comment below.

For more articles about API testing , please go to link : https://testerpath.com/category/api-testing/

Leave a Reply

Your email address will not be published. Required fields are marked *

API testing

How to test API

After reading “test API with Postman” series, you should be able to grasp the basic knowledge of the API and the functions Postman provides. But how to arrange tests and write Testcases for API still seems not very clear, so today I will write a post about how to test API properly. Reminder of knowledge […]

API testing

API testing – API documentation

Postman, in addition to providing an API testing tool, also helps us to make API documentation extremely professional and easy. This API document can be shared by both the team and the client. Usually, the API is usually written by Dev on google sheets, but at a certain stage of development, the dev will be […]

API testing

API Testing – Postman pre request script

In the previous article, I wrote about test Response, now I will continue to write about Postman pre request script. Here are the steps when sending a request. The Pre-request part will be the part Postman will process before sending the request, and the test script to handle the returned response. So what can Pre-request […]