Skip to content
Postman API Testing Tips

How To Test A Web Service Using Postman

API Testing Blog

Getting Started with Postman for Web Service Testing

Postman is a powerful tool for interacting with APIs, making it ideal for testing web services. It offers a user-friendly interface for sending requests, inspecting responses, and automating tests. In this guide, we’ll explore the basics of using Postman for web service testing, including sending requests, validating responses, and setting up automated tests.

1. Setting up Your Environment

  • Install Postman: Download and install Postman from https://www.postman.com/. Choose the appropriate version for your operating system.
  • Create a Workspace: Workspaces in Postman allow you to organize your requests, collections, and environments. Click the “Create Workspace” button and give it a meaningful name.

2. Sending Your First Request

  • Open the Postman App: Launch the Postman app.
  • Create a New Request: Click the “New” button in the top left corner of the screen.
  • Choose a Request Method: Select the appropriate HTTP method (GET, POST, PUT, DELETE, etc.) for your request from the dropdown menu.
  • Enter the Request URL: Fill in the URL of the web service endpoint you want to test in the “Enter request URL” field.
  • Set Request Headers: Click the “Headers” tab and add any necessary headers for your request. For example, you may need to set the “Content-Type” header to “application/json” if you’re sending a JSON payload.
  • Add Request Body: If your request requires a body (like POST, PUT, or PATCH requests), click the “Body” tab and select the format of your payload (e.g., JSON, form data, raw). Fill it with the appropriate data.
  • Send the Request: Click the “Send” button to execute your request.

Example:

Let’s say we want to test a GET request to fetch a list of users from a RESTful API:

// Request URL
https://api.example.com/users


// Request Headers
Content-Type: application/json

Sample Code (JSON Body):

{
  "name": "John Doe",
  "email": "john.doe@example.com"
}

3. Inspecting the Response

Once you send your request, Postman will display the response from the web service. You can inspect several aspects:

  • Status Code: The HTTP status code indicates the outcome of the request (e.g., 200 for success, 404 for not found, 500 for server error).
  • Headers: Examine the response headers, which provide additional information about the response, such as the content type or server information.
  • Body: The response body contains the data returned by the web service. It can be in various formats, including JSON, XML, or plain text. Postman provides tools to format and view the body in a readable manner.

4. Validating the Response

  • Assertions: For comprehensive testing, you need to ensure the response meets your expectations. Postman provides features for assertion testing. You can use the “Test” tab to write code (often in JavaScript) that checks specific aspects of the response, such as:
    • Status Code: Verify that the response code is the expected one.
    • Response Body: Check if the response body contains specific data.
    • Response Time: Measure the time it takes for the service to respond.
  • Example (JavaScript test code):
pm.test("Status code is 200", function () {
    pm.response.to.have.status(200);
});


pm.test("Response contains 'John Doe'", function () {
    pm.expect(pm.response.text()).to.include("John Doe");
});

5. Creating Collections for Organization

  • Organize Requests: Collections are a fundamental concept in Postman. They allow you to group related requests together for easy management. To create a collection, click the “Collections” button in the left sidebar, then “Create Collection.”
  • Add Requests to a Collection: Once you have a collection, you can add individual requests to it. Each request will be stored within the collection for easy access and reusability.

6. Using Environments and Variables

  • Environments: Environments help you manage different configuration settings for various environments (like development, testing, and production).

  • Variables: Variables allow you to store values that can be reused across multiple requests. For example, you can store the base URL of a web service in an environment variable, then reference it in your requests.

  • Example (environment variable):

// Environment variable name: apiBaseUrl
// Environment variable value: https://api.example.com

You can then reference this variable in your request URL:

{{apiBaseUrl}}/users

7. Automating Tests with Postman Collections

  • Adding Tests: You can add tests to individual requests or to the collection level. Collection-level tests run after each request in the collection, helping you verify the overall flow of your API interactions.
  • Runner Tool: Postman’s Runner tool enables you to execute your collections and tests automatically. It allows you to set up iterations, data-driven testing, and reports for comprehensive testing.

8. Debugging and Troubleshooting

  • Console Log: Utilize the console.log() function in your test scripts to log messages and variables for debugging.
  • Postman Console: Postman provides a built-in console where you can inspect errors, network requests, and other information related to your requests.
  • Response Body: Carefully inspect the response body for any error messages or unexpected data.
  • Network Inspector: Use your browser’s built-in network inspector (e.g., Chrome’s Developer Tools) to analyze the network communication and identify issues.

9. Sharing and Collaboration

  • Shared Workspaces: Postman allows you to share workspaces with your team members for collaborative testing and API development.
  • Exporting and Importing: You can export your collections and environments into JSON files and import them into other Postman instances.

By leveraging Postman’s features, you can efficiently test web services, validate responses, and automate comprehensive testing processes. This will help ensure the quality and reliability of your API.

API Testing Blog