<div class="post-toc-block float-default with-border"> 
						<div class="post-toc-header">Table of Contents</div>
						<nav id="md-post-toc" class="md-post-toc"></nav>
						</div>Hey! Testing keploy with postman APIs by making API calls and checking if the response is right or not (manually) is a frustrating task.🥱

I have been exploring different ways to automate testing. So, next time I don’t have to execute the same things again.🕵️‍♀️
Over the period of last few weeks, I have been exploring and experimenting with various testing tools and frameworks, and during that. I explored writing test-automation scripts but I could see forehand that it was going to take time. So, I looked into all these popular fancy <a href="https://keploy.io/blog/community/mastering-api-test-automation-best-practices-and-tools">Test Automation</a> Tools and tried 2 from the extreme ends&#8230; Postman (popular, mature closed-source, widely adopted) and Keploy (no-code, new open-source, secondarily adopted).
I found that with Postman, along with API management I can write test scripts for my cases and assert the API responses using the Postman test snippet feature.
I initially used the Postman test snippet to write test cases and used it to run the test collection that I built eventually but I was a little exhausted because the test cases broke so often.
Why did they break? It was not me! It was not the code changes! It was the database!! Many times the API response changed because my team member changed the database my application was talking to! &#8230;😢
I soon realised I need to change all the test scripts I wrote in Postman and make sure NOBODY messes up with my test database or else I&#8217;d need to do the same again.
Then, I looked for more testing automation tools like Rest Assured, Selenium, Katalon, etc… but these also required writing test cases, and test database.
After this, I started looking for no-code test automation tools and found Keploy with which I was able to record Postman API calls as a test case and the best part was I didn&#8217;t need to keep my test database.
In this article, I will brief about the steps that I took to automate my test cases on both Postman and Keploy:
<ol>
<li>Setting up a sample application(URL Shortener) locally — optional</li>
<li>Creating test snippets in Postman</li>
<li>Recording test cases in Keploy</li>
</ol>
Moving on to the first step…
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656686338527/Qzaw1BU7y.png" alt="1_iFZEf3i8zVc54W3Dmr4Fcw.png" />
Let&#8217;s take one sample application and write test cases for the same using both Postman and Keploy. Clone and run a sample URL Shortener application locally
<pre><code>git clone https://github.com/keploy/samples-go &amp;&amp; cd samples-go/echo-sql

go mod download</code></pre>
Start the PostgreSQL instance in Docker for this sample application. 
In Postgres DB the sample application is storing the shortened URL for a given long URL.
<pre><code>docker-compose up -d</code></pre>
Now open a new terminal and run the sample application
<pre><code>go run handler.go main.go</code></pre>
Doing this you will start the localhost server for the URL shortener application.
<h2>Now we can try making some API calls and testing keploy with postman</h2>
Let’s Post a long URL, say, github.com , which will add a shortened URL in the database.
You can import the following curl into Postman
<pre><code>curl --request POST \
 --url http://localhost:8080/url \
 --header 'content-type: application/json' \
 --data '{
 "url": "https://github.com"
}'</code></pre>
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656695533749/-f8smtQ6N.png" alt="Adding an URL for the API call" />
After making the API call, you will get the shortened URL for github.com
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656696111606/YrJDghNza.png" alt="1_XBRU8kAMJN2fTYP7eqtZ6A.png" />
Let make another API call to GET the shortened URL content.
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656696383680/D6bliJyt7.png" alt="1_jEX2Sru0geODw28Y5PLq5Q.png" />
<pre><code>curl --request GET \
 --url http://localhost:8080/GuwHC</code></pre>
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656696419111/egqOZCx_p.png" alt="1_oG5T4Jr3tlkdLqRlnx-osQ.png" />
Since we understood both the API of the sample application, lets automate the testing for these APIs.
<h2>Creating test snippets in Postman</h2>
Moving towards the testing of this API!
I will be making the following testcases here:
<ol>
<li>Status code</li>
<li>Response Time</li>
</ol>
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656707598315/wXT3lQ4I5.png" alt="1_fsKg7sF6C_3WZyH81QADEw.png" />
Now, as I have done above.
Just to check if my request gives me a status 200/201/202 etc, or to check the response Time, I have to manually write testcases in Postman.
This seems plausible when the testing is done on a small scale.
What would you do if you have an API with 1000+ data in it and you have to verify each of its content?
<h2>Recording test cases in Keploy</h2>
To get started with Keploy, I will follow the below steps:
<pre><code>git clone https://github.com/keploy/keploy.git &amp;&amp; cd keploy
docker-compose up</code></pre>
Once the Keploy server is up and running, we will start our application server over localhost.
To do that, run the following command in the terminal.
<pre><code>docker-compose up -d
go run handler.go main.go</code></pre>
Once the server is setup, run your Postman as usual and make API calls.
Keploy locahost can be accessed on localhost:8081 and you can use the following link to get to the test cases directly
<pre><code>http://localhost:8081/testlist</code></pre>
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656708508628/wWoLXvjwA.png" alt="1_Ct6UYDGrEyUA29RfHdPwBA.png" />
As you can see, we have our testcases generated by Keploy and now we just need to start testing.
Moving forwards, kill your localhost and run the below command to do run testing
<pre><code>go test -coverpkg=./... -covermode=atomic ./...</code></pre>
this should show you have 74.4% coverage without writing any code!
Start your server again with
<pre><code>go run handler.go main.go</code></pre>
go back to keploy localhost and check the Test runs
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656708579755/M9Ws-9ULh.png" alt="1_mhMufdbp5GCeuoKRQZZUyg.png" />
TestRun for the API
<img decoding="async" src="https://cdn.hashnode.com/res/hashnode/image/upload/v1656708587596/2jSF9D3Ut.png" alt="1_QbTKnXAKzpY2uLJsBGwfAw.png" />
TestRuns of our API calls
You can find that Keploy has done in total 6 tests and each tests have Passed.
The major point here is that we didn’t made any test case on our own🤩!
<h2>Concluding</h2>
We just did API, Testing Keploy with Postman and as we experienced,
I had to add test cases using snippets when testing using Postman and the test database needs to be maintained in long term.
Whereas I didn’t have to write a test script to do the testing in <a href="https://keploy.io/">Keploy</a>, it&#8217;s not a very big plus, what I liked the most was that the database calls were also recorded and I don&#8217;t have to set up that test database again.
This is it for now!&#8230; I will be coming up with more approaches I explored with different testing tools.
Wishing you error-free API delivery! 😁
Don’t forget to give me a follow as I’ll publish more such blogs related to APIs and Testing 😁
— by <a href="https://twitter.com/curlyParadox">Nishant Mishra</a>

 
 
 

 
 <div class="pp-multiple-authors-boxes-wrapper pp-multiple-authors-wrapper pp-multiple-authors-layout-boxed multiple-authors-target-the-content box-post-id-16 box-instance-id-1 ppma_boxes_16"
 data-post_id="16"
 data-instance_id="1"
 data-additional_class="pp-multiple-authors-layout-boxed.multiple-authors-target-the-content"
 data-original_class="pp-multiple-authors-boxes-wrapper pp-multiple-authors-wrapper box-post-id-16 box-instance-id-1">
 <h2 class="widget-title box-header-title">Author</h2>
 
 <div class="ppma-author-category-wrap">
 
 <ul class="pp-multiple-authors-boxes-ul">
 <li class="pp-multiple-authors-boxes-li author_index_0 author_nishant-mishra has-avatar">
 <div class="pp-author-boxes-avatar">
 <img alt='Nishant Mishra' src='https://wp.keploy.io/wp-content/uploads/2024/10/nishant-mishra.jpg' srcset='https://wp.keploy.io/wp-content/uploads/2024/10/nishant-mishra.jpg' class='multiple_authors_guest_author_avatar avatar' height='80' width='80'/> </div>
 
 <div class="pp-author-boxes-avatar-details">
 <div class="pp-author-boxes-name multiple-authors-name">
 <a href="https://wp.keploy.io/author/nishant-mishra/" rel="author" title="Nishant Mishra" class="author url fn">Nishant Mishra</a> 
 </div>
 
 I'm Nishant Mishra, a seasoned Software Engineer passionate about creating innovative solutions and staying ahead of industry trends. I thrive in fast-paced tech environments and am open to discussions, collaborations, and new opportunities in software development and emerging technologies. 
 <a class="ppma-author-user_url-profile-data ppma-author-field-meta ppma-author-field-type-url" aria-label="Website" href="https://www.linkedin.com/in/curlyparadox/" rel="dofollow" target="_blank"> </a>
 
 </div>
 </li>
 </ul>
 
 </div>
 
 </div>
 
 
 
 <style>
 .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-avatar img { width: 80px !important; height: 80px !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-avatar img { border-style: none !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-avatar img { border-radius: 50% !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-meta a { background-color: #655997 !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-meta a { color: #ffffff !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-meta a:hover { color: #ffffff !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .ppma-author-user_email-profile-data { background-color: #655997 !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .ppma-author-user_email-profile-data { border-radius: 100% !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .ppma-author-user_email-profile-data { color: #ffffff !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .ppma-author-user_url-profile-data { background-color: #655997 !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .ppma-author-user_url-profile-data { border-radius: 100% !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .ppma-author-user_url-profile-data { color: #ffffff !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-author-boxes-recent-posts-title { border-bottom-style: dotted !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-multiple-authors-boxes-li { border-style: solid !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-multiple-authors-boxes-li { border-width: 1px !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-multiple-authors-boxes-li { border-color: #999 !important; } .pp-multiple-authors-boxes-wrapper.box-post-id-16.pp-multiple-authors-layout-boxed.multiple-authors-target-the-content.box-instance-id-1 .pp-multiple-authors-boxes-li { color: #3c434a !important; } </style>

My journey of Automating Test Cases!

Getting Started with Microservices Testing

Python Switch Case: How to Implement Switch Statements in Python

Getting Started with Alpha Testing : Definition, Process, and Key Benefits

How to Use Python Code for Pulling API Data Efficiently

Gemini 2.5 Pro vs OpenAI o1: Benchmarking AI Models for Software Testing

Unit Testing vs Regression Testing: A Comprehensive Guide

Smoke Testing vs Regression Testing: What You Need to Know

Building Keploy.io, an EBPF based open source framework to generate test cases and data stubs from API calls.

Neha Gupta

Cloud technology veteran and probably the youngest (globally) to have completed all 5 AWS certifications (including Solutions architect Professional and Dev­ops engineer professional)

My Journey Of Automating Test Cases!

More Stories