<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Akash Kumar</title>
    <description>The latest articles on DEV Community by Akash Kumar (@akash_kumar_9b8fa1b422d64).</description>
    <link>https://dev.to/akash_kumar_9b8fa1b422d64</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3302190%2F2d42f83c-2f60-40ad-be0a-657112be67c2.jpg</url>
      <title>DEV Community: Akash Kumar</title>
      <link>https://dev.to/akash_kumar_9b8fa1b422d64</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akash_kumar_9b8fa1b422d64"/>
    <language>en</language>
    <item>
      <title>🧠 From Building Habits to Breaking Testing Barriers – My API Testing Journey with Keploy</title>
      <dc:creator>Akash Kumar</dc:creator>
      <pubDate>Sat, 28 Jun 2025 06:11:07 +0000</pubDate>
      <link>https://dev.to/akash_kumar_9b8fa1b422d64/from-building-habits-to-breaking-testing-barriers-my-api-testing-journey-with-keploy-228o</link>
      <guid>https://dev.to/akash_kumar_9b8fa1b422d64/from-building-habits-to-breaking-testing-barriers-my-api-testing-journey-with-keploy-228o</guid>
      <description>&lt;p&gt;Building APIs is fun — but testing them? That used to feel like a chore.&lt;br&gt;
As part of the Keploy GitHub Learning Program, I recently built a full-stack Habit Tracker API using Flask and MongoDB — but the real shift came when I got to test it using AI.&lt;/p&gt;

&lt;p&gt;📌 The Project: Habit Tracker API&lt;/p&gt;

&lt;p&gt;The idea was simple — track personal habits for different users with full CRUD operations. I built:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A custom REST API in Flask

A MongoDB backend

A basic HTML + JavaScript frontend for testing

5 core endpoints: Add, Get, Update, and Delete habits
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Sounds complete, right? Almost. But what about testing?&lt;br&gt;
😫 The Problem: Manual API Testing&lt;/p&gt;

&lt;p&gt;Initially, I tried writing unit tests manually — and it worked, but:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;It was time-consuming

I struggled to cover all use cases

Every time I changed my API, I had to update my tests again
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;That’s when Keploy entered the scene.&lt;br&gt;
🤖 The Game Changer: Keploy's AI Testing&lt;/p&gt;

&lt;p&gt;With Keploy CLI, I was able to:&lt;/p&gt;

&lt;p&gt;✅ Automatically record API calls&lt;br&gt;
✅ Replay them as test cases&lt;br&gt;
✅ Achieve real test coverage without manually scripting each test&lt;/p&gt;

&lt;p&gt;I used curl commands and the frontend UI to simulate real use, while Keploy silently captured everything — and then turned those interactions into executable test cases.&lt;br&gt;
Literally zero code for test writing!&lt;/p&gt;

&lt;p&gt;🛠️ CI/CD Integration with GitHub Actions&lt;/p&gt;

&lt;p&gt;Testing alone isn’t enough — it needs to be automated.&lt;/p&gt;

&lt;p&gt;So I went ahead and:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Created an OpenAPI schema (using Flasgger)

Integrated Keploy test execution in GitHub Actions

Ensured my pipeline runs tests on every push and pull request
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;This step made my API production-ready in the truest sense.&lt;br&gt;
🌐 Chrome Extension Bonus&lt;/p&gt;

&lt;p&gt;To take it one step further, I used Keploy’s Chrome Extension to test APIs on real-world websites.&lt;br&gt;
It felt amazing to inspect network traffic and capture meaningful test data without dev tools or Postman.&lt;/p&gt;

&lt;p&gt;💡 What I Learned&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Testing doesn’t have to be painful.

AI + DevTools = game-changing productivity

CI/CD is not complete without reliable test automation

Real coverage &amp;gt; theoretical coverage
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;🧩 Tech Stack Used&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Backend: Flask (Python), MongoDB

Frontend: HTML + JS

Testing: Keploy CLI, Keploy Chrome Extension

CI/CD: GitHub Actions
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;🔗 See it in action:&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://github.com/404AkashNotFound/habit-tracker-api.git" rel="noopener noreferrer"&gt;GitHub Repo Link – Habit Tracker API&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Big shoutout to &lt;a class="mentioned-user" href="https://dev.to/keploy"&gt;@keploy&lt;/a&gt;  for building such a developer-friendly tool and helping students like me explore test automation with real-world projects.&lt;/p&gt;

&lt;p&gt;Want to test APIs like a pro?&lt;br&gt;
Try Keploy — you might just fall in love with testing 💙&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
