It is a set of variables that differentiate among the requests. Such as, we can have an environment for testing, one for development and another for production. We can change the value of the variables to pass the data between requests and tests<\/span><\/p>\n The Payload of an API Module is the body of your request and response message. It contains the data that you send to the server when you make an API request. You can send and receive Payload in different formats, for instance JSON.<\/span><\/p>\n Pre-request scripts in Postman to execute JavaScript before a request runs<\/p>\n Scripts in the Pre-request Script tab for a request, collection, or folder, you can carry out pre-processing such as setting variable values, parameters, headers, and body data<\/p>\n It will help for debugging code by logging the output in the console<\/p>\n Postman resolves scopes according to a variable scope hierarchy. Using variables within specific scopes allows you to reuse values efficiently.<\/p>\n Postman supports the following variable scopes:<\/p>\n Global variables <\/b>allow you to access data between collections, requests, test scripts, and environments. Global variables are available throughout a workspace.<\/p>\n Collection variables <\/b>are available throughout the requests in a collection and are independent of environments, so do not change based on the selected environment.<\/p>\n Environment variables <\/b>allow you to tailor your processing to different environments, for example local development vs testing or production. Only one environment can be active at a time.<\/p>\n Local variables <\/b>are temporary, and only accessible in your request scripts. Local variable values are scoped to a single request or collection run, and are no longer available when the run is complete.<\/p>\n Data variables<\/b> come from external CSV and JSON files to define data sets you can use when running collections via Newman or the Collection Runner.<\/p>\n For every request in a collection, scripts will execute in the following order:<\/p>\n In Postman, the script execution order for a single request looks like this:<\/p>\n Postman uses the faker library to generate dummy data. You can generate random names, addresses, email addresses, and much more. You can use these pre-defined variables multiple times to return different values per request<\/p>\n You can use these variables like any other variable in Postman. Their values are generated at the time of execution and their names start with a $ symbol<\/p>\n e.g. $guid, $timestamp etc.<\/p>\n To use dynamic variables in pre-request or test scripts, you need to use pm.variables.replaceIn(),<\/p>\n e.g. pm.variables.replaceIn(‘{{$randomFirstName}}’).<\/p>\n We can debug written scripts by using Pre-request Script or Tests tabs, and we can validate log messages using the Postman console.<\/p>\n Postman console helps debug our requests when an API isn’t behaving as we expect<\/p>\n Using the console: <\/b>Below log statements at appropriate locations in our test scripts will help you identify the source of any issues. Every request sent by Postman is logged in the console, so you can view the detail of what happened when you sent a request.<\/p>\n open the console from the status bar on the bottom left of Postman or selecting View > Show Postman Console<\/p>\n Accessing console logs: <\/b>Access the DevTools console logs, open the View menu and select Show DevTools. In the DevTools window, click Console to see the app debug logs.<\/p>\n Using the monitor console log: <\/b>Refer left panel for monitor control, Create a monitor based on collection\/environment and select the Console Log tab. This will display monitor run details, along with the console.log from pre-request and test scripts.<\/p>\n Chai assertion library<\/b> is available by default in the Postman. So when you are writing chai assertions, then don’t worry about other processes of installation.<\/p>\n The main feature of Postman assertions is that they write the tests with English sentences, which is human readable. So it is very easy to read and user friendly.<\/p>\n Example Chai BDD expect assertion:<\/strong><\/p>\n You can handle this by disabling SSL certificate verification in Postman. Settings->SSL certificate verification<\/b><\/p>\n Postman provides JavaScript APIs that you can use in your request scripts.<\/p>\n The pm<\/b> object provides most of the functionality for testing your request and response data, with the postman object providing some additional workflow control.<\/p>\n Request parameters are used to send additional information to the server. A request URL contains these parameters.<\/p>\n Path<\/b> parameters form part of the request URL, which are referenced using placeholders preceded by \u2018:\u2019<\/p>\n Query<\/b> parameters are appended to the end of the request URL, following \u2018?\u2019 and listed in key<\/p>\n value pairs, separated by \u2018&\u2019using the following syntax: ?id=1&type=new<\/p>\n4. What is payload in Postman?<\/b><\/h3>\n
<\/b><\/h2>\n
5. What is a Pre-request script in Postman? <\/b><\/h3>\n
<\/p>\n
6. Could you explain about Postman Variable scopes?<\/b><\/h3>\n
\n
<\/p>\n
7. What is the Postman execution order for a collection?<\/b><\/h3>\n
\n
<\/p>\n
8. What is the Postman execution order for a single request?<\/b><\/h3>\n
\n
<\/p>\n
9. How do you set a dynamic variable in Postman?<\/b><\/h3>\n
10. How do you debug your collections, pre-request, test scripts in Postman?<\/b><\/h3>\n
\n
11. How do you use an assertion in the Postman?<\/b><\/h3>\n
<\/p>\n
12. How to handle a self-signed certificate with Postman? <\/b><\/h3>\n
13. What is pm object in postman?<\/b><\/h3>\n
14. What is path and query parameter in Postman? <\/b><\/h3>\n