Explore topic-wise InterviewSolutions in Current Affairs.

The request history can be accessed in the History tab provided on the Postman application. If we sign into the Postman account, then the history will be synced ACROSS the devices where you are logged in.

• When you click on any of the requests present in the History tab, the view OPENS the request that we have saved while we were working on it earlier.
• History also consists of the collection runs that were EXECUTED as summarized versions. They are not logged in History as single requests.
• Click on “View More option (…)” on the request, we will see options to SAVE, document, monitor, delete or mock the request.
• Multiple requests can be selected by USING Command or Control button and then clicking on the request.

The following image shows the page that shows when you click on View More Option upon a request present in the History tab:

Image Source: Postman Learning Documentation

301 status code REPRESENTS PERMANENT redirect from one website page to another. It TELLS the SEARCH engine that the old page is outdated and the engine has to index the new page URL.

We can do this in two ways:

1. Click on the Download BUTTON in the RESPONSE section.
2. Click on the ARROW beside send button - There will be an option to send and download. Clicking on it will prompt Postman to ask the location of saving the response post SUCCESSFUL execution of the REQUEST.

• Postman is not suitable for PROCESSING 1000+ API REQUESTS.
• If the project is very large, managing the collections and requests become cumbersome.
• It is not suitable if we want to manage the workspace in the FORM of code as there would be a LOT of code duplication for dynamic API requests.

The BINARY form is designed to HELP SEND DATA in a format that is not possible to be ENTERED manually. These options are used while sending large files like images, CSV files, etc in the POST request. Binary representation is the easiest representation for sending complex data with the request.

Monitoring is a method of staying in sync with the health and PERFORMANCE of the APIs. Postman PROVIDES inbuilt monitoring services that help us be in sync with the API development and performance. The monitors provided by Postman are mainly based on the working of collection RUNNERS. They run every request in the collection and analyze the values MENTIONED in the TEST scripts. Monitors use the test scripts for validating and monitoring the responses. The reports generated are shared with the developers over emails or alerts in slack, hipchat, etc based on our configuration settings.

The scope of GLOBAL variables is LIMITED to the workspace and is global. DUE to this, variables having global scope cannot have the same names. We can have the same names for local variables but they need to be part of different variables.

Postman ACCEPTS authorization CREDENTIALS in Base64 encoding format only. It is provided in Postman by default. If we do not want to USE an inbuilt encoding system, we can refer to third-party WEBSITES for CONVERTING the credentials in base64 format.

DIGEST Authorization is one of the authorization techniques provided by Postman. In this technique, the client first sends the request to the API and get responses from the server including a number which is usable only once, a REALM value and 401 unauthorized response. We will be then SENT back an encrypted data array having both username and password along with the data received from the server earlier. The server uses this data to generate an encrypted data string and compares this with what was sent for authenticating the request.

We can do this by selecting the Authorization TAB, then selecting “Digest Auth” from the drop-down list. Postman window presents the fields for both stages of the authentication request. The fields required for the second stage of the request are auto-filled based on the data received from the server. For more information, you can refer here.

Basic Auth in Postman is a TYPE of AUTHORIZATION technique provided in Postman for HTTP user agents like web browsers. It provides fields to ENTER USERNAME and PASSWORD which when entered gets associated with the request.

Path Variables are USED for IDENTIFYING specific resources and Query PARAMETERS are used for sorting or FILTERING the resources.

POSTMAN SUPPORTS the FOLLOWING TYPE of REQUESTS:

• GET
• POST
• PUT
• PATCH
• DELETE
• COPY
• HEAD
• OPTIONS
• LINK
• UNLINK
• PURGE
• LOCK
• UNLOCK
• PROPFIND
• VIEW

POSTMAN PROVIDES the below API request AUTHORIZATION Options:

• API Key
• Bearer Token
• Basic auth
• Digest auth
• Oauth 1.0
• Oauth 2.0
• Hawk Authentication
• AWS Signature
• NTLM Authentication

It can be ACCESSED by USING the VARIABLE NAME as:{{variable_name}}

We can LOG the variable values in Postman in the CONSOLE by USING the command:
console.log(pm.variables.get("variable_name"));

We use Postman for the below reasons:

• Firstly, Postman is free software that is USEFUL for API TESTING.
• It can send HTTP requests of various types (such as GET, POST, PUT, PATCH, etc) and gives the ability to save ENVIRONMENTS for future use.
• It helps in managing the end-to-end lifecycle of the API - starting from design to mocking to testing and finally maintaining the APIs.
• It PROVIDES Runtime Service that helps in managing API collections, environments, work-spaces, and different examples.
• It can be used to easily integrate with CI/CD TOOLS such as Jenkins.
• Has extensive support from the community and provides extensive documentation.

A collection in Postman HELPS to group SIMILAR REQUESTS. It helps in SYSTEMATICALLY arranging the requests into folders.

Postman is a free, HTTP Client based software application primarily used to perform API testing. It supports testing of HTTP requests by utilizing GUI (Graphical User Interface) which can be executed and the responses can be validated. It also helps in COLLABORATING among the TEAM MEMBERS for the development of API by providing a platform to design, develop, test, and document APIS.