DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Building Multi-Rail Payment Failover to Stop Latency Spikes and Double Debits
  • GET, POST, PUT, DELETE: Choosing HTTP Verbs in a Real .NET Core Web API, Not Just by the Textbook
  • Delegated Transport, Forked Authorization: Where Chat and AI-Agent Integrations Actually Break
  • A Non-Expiring AKS Deployment Token Could Read Secrets Across Three Namespaces

Trending

  • PWA on iOS, Part 2: HTTPS, Manifest and Service Worker
  • Fix the Target, Precompute Once: A Backend-Free Word-Ladder Solver With a BFS Distance Field
  • The Permission Was Valid. The Action Was Not Authorized.
  • Should Developers Switch From SQLite to DuckDB?

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. How to Verify API Responses in Katalon Studio

How to Verify API Responses in Katalon Studio

Learn how to verify API responses when performing API testing in Katalon Studio.

By 
Oliver Howard
·
Nov. 08, 18 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
15.2K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

Verifying an API response is always a challenging task in API testing. Some testers may find it hard to understand the JSON/XML response format; while some others struggle with getting the value of a specific key to verify. It is even harder when the response is big enough with the complex data structure.

Starting from version 5.8.3, Katalon Studio has released a new feature that targets solving those issues with a simple step. In this tutorial, you will learn how to use this feature to verify API responses.

If you haven’t created any API tests using Katalon Studio, please follow this link (Create your first API test with Katalon Studio) to get familiar with the tool.

Verifying REST Responses in JSON Format

Assume that you have run an API, which returned a response in JSON format

Image title

The below steps will show you how to verify the response:

(1) Hover your cursor over the property you want to verify.

(2) You will see the information about JsonPath of the property you want to verify. Press the compose key “Ctrl + K” (on Windows) or “Cmd + K” (on Mac).

(3) A statement will be generated to verify the selected property.

Verifying SOAP Responses in XML Format

Assume that you have run an API, which returned a response in XML format

Image title

The steps below will help you verify the response:

(1) Hover your cursor over the element you want to verify.

(2) You will see the information about XmlPath of the element you want to verify. Press the compose key “Ctrl + K” (on Windows) or “Cmd + K” (on Mac).

(3) A statement will be generated to verify the selected element.

Run Tests With Generated Verification Statements

To run both types of request with the generated verification statements, you need to choose the option “Test Request and Verify”.

Image title

(1) First, select “Test Request and Verify” from the Run menu to send the request and verify the response.

(2) The verification results will be displayed in the Verification Log tab.

Congrats! You have successfully verified the response in both JSON and XML formats without having to know how to get JsonPath or XmlPath. We hope this tutorial will help remove the difficulty of verifying API responses.

API Katalon Studio

Published at DZone with permission of Oliver Howard. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Building Multi-Rail Payment Failover to Stop Latency Spikes and Double Debits
  • GET, POST, PUT, DELETE: Choosing HTTP Verbs in a Real .NET Core Web API, Not Just by the Textbook
  • Delegated Transport, Forked Authorization: Where Chat and AI-Agent Integrations Actually Break
  • A Non-Expiring AKS Deployment Token Could Read Secrets Across Three Namespaces

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook