<?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: Ashish Singh</title>
    <description>The latest articles on DEV Community by Ashish Singh (@drashish987).</description>
    <link>https://dev.to/drashish987</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3301336%2F9555a450-5e86-4bfb-9889-a51eb19e73c4.jpeg</url>
      <title>DEV Community: Ashish Singh</title>
      <link>https://dev.to/drashish987</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/drashish987"/>
    <language>en</language>
    <item>
      <title>How I Went from 0% to 100% API Test Coverage in Minutes Using Keploy</title>
      <dc:creator>Ashish Singh</dc:creator>
      <pubDate>Fri, 27 Jun 2025 19:57:30 +0000</pubDate>
      <link>https://dev.to/drashish987/how-i-went-from-0-to-100-api-test-coverage-in-minutes-using-keploy-10nn</link>
      <guid>https://dev.to/drashish987/how-i-went-from-0-to-100-api-test-coverage-in-minutes-using-keploy-10nn</guid>
      <description>&lt;p&gt;🔍 Day 4 of My API Testing Journey — Manual to AI in No Time&lt;br&gt;
As a backend developer, writing APIs is exciting. But testing them manually? Not so much. Writing, mocking, asserting — it's time-consuming and error-prone.&lt;/p&gt;

&lt;p&gt;Then I found Keploy – an open-source, AI-powered API testing toolkit. It changed my workflow overnight! 💥&lt;/p&gt;

&lt;p&gt;🔧 What I Built&lt;br&gt;
✅ Book Management API using Node.js + Express + MongoDB&lt;br&gt;
✅ Created an OpenAPI Schema&lt;br&gt;
✅ Tested using Keploy CLI&lt;br&gt;
✅ Used Keploy Chrome Extension for real-world testing&lt;br&gt;
✅ Integrated with GitHub Actions for automated CI testing&lt;br&gt;
✅ Achieved 100% test suite coverage with smart mocking 🧠&lt;/p&gt;

&lt;p&gt;📊 My Keploy Test Report&lt;/p&gt;

&lt;p&gt;🔄 160 Test Suites&lt;/p&gt;

&lt;p&gt;✅ 95 Accepted&lt;/p&gt;

&lt;p&gt;❌ 65 Rejected&lt;/p&gt;

&lt;p&gt;This was done without writing a single line of manual tests! 🤯&lt;/p&gt;

&lt;p&gt;🌐 Real-World API Testing&lt;br&gt;
I tested public APIs with the Keploy Chrome Extension:&lt;/p&gt;

&lt;p&gt;🔸 openweathermap.org – real-time weather data&lt;br&gt;
🔸 fakestoreapi.com – eCommerce product listings&lt;/p&gt;

&lt;p&gt;Keploy captured the API traffic and converted it into reusable, replayable test cases — no mocks or scripts needed.&lt;/p&gt;

&lt;p&gt;⚙️ Why Keploy is a Game-Changer&lt;br&gt;
Manual Testing  Keploy AI Testing&lt;br&gt;
❌ Write tests manually    ✅ Auto-generated from traffic&lt;br&gt;
❌ Mock DB/API manually    ✅ Auto-mocked&lt;br&gt;
❌ Tedious CI setup    ✅ Simple GitHub Action&lt;br&gt;
❌ Missed edge cases   ✅ Smart assertions included&lt;/p&gt;

&lt;p&gt;Keploy eliminated repetitive test writing and focused on real usage-based testing. It’s like having an AI test co-pilot.&lt;/p&gt;

&lt;p&gt;🔨 Tools &amp;amp; Stack I Used&lt;br&gt;
Node.js + Express&lt;/p&gt;

&lt;p&gt;MongoDB&lt;/p&gt;

&lt;p&gt;Keploy CLI + Agent&lt;/p&gt;

&lt;p&gt;Keploy Chrome Extension&lt;/p&gt;

&lt;p&gt;GitHub Actions (CI/CD)&lt;/p&gt;

&lt;p&gt;OpenAPI &amp;amp; curl&lt;/p&gt;

&lt;p&gt;📂 Project Resources&lt;br&gt;
🔗 GitHub Repo: Drashish987/Api-testing-&lt;/p&gt;

&lt;p&gt;📄 OpenAPI Schema: openapi.yaml&lt;/p&gt;

&lt;p&gt;⚙️ CI/CD Workflow: keploy.yml&lt;/p&gt;

&lt;p&gt;🧠 What I Learned&lt;br&gt;
Test coverage doesn’t have to be hard&lt;/p&gt;

&lt;p&gt;AI tools like Keploy save time and effort&lt;/p&gt;

&lt;p&gt;Testing with real traffic is more reliable than mocks&lt;/p&gt;

&lt;p&gt;GitHub Actions + Keploy is a perfect CI combo&lt;/p&gt;

&lt;p&gt;💬 Final Thoughts&lt;br&gt;
Thanks to Keploy, I finally enjoyed API testing 😄&lt;br&gt;
It made testing feel like a natural part of building, not a separate, frustrating chore.&lt;/p&gt;

&lt;p&gt;If you build APIs, try Keploy. Trust me, you’ll never go back to writing tests manually.&lt;/p&gt;

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