<?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: Ankita Kumari</title>
    <description>The latest articles on DEV Community by Ankita Kumari (@ankita2311).</description>
    <link>https://dev.to/ankita2311</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%2F3303093%2Ff1120e02-490c-400d-8d86-8ead86b1cad6.png</url>
      <title>DEV Community: Ankita Kumari</title>
      <link>https://dev.to/ankita2311</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ankita2311"/>
    <language>en</language>
    <item>
      <title>🚀 Building and Testing a Dockerized Book API with Keploy</title>
      <dc:creator>Ankita Kumari</dc:creator>
      <pubDate>Sat, 28 Jun 2025 13:25:48 +0000</pubDate>
      <link>https://dev.to/ankita2311/building-and-testing-a-dockerized-book-api-with-keploy-6ab</link>
      <guid>https://dev.to/ankita2311/building-and-testing-a-dockerized-book-api-with-keploy-6ab</guid>
      <description>&lt;p&gt;Over the past week, I worked on an exciting project — building a RESTful Book API using Node.js, containerizing it with Docker, and automating test generation using Keploy. Here’s a complete walkthrough of what I built, learned, and achieved!&lt;/p&gt;

&lt;p&gt;🔧 Tech Stack&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Technology&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Language&lt;/td&gt;
&lt;td&gt;JavaScript (Node.js)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Framework&lt;/td&gt;
&lt;td&gt;Express.js&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Database&lt;/td&gt;
&lt;td&gt;PostgreSQL (via Docker)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DB Client&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;pg&lt;/code&gt; (node-postgres)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Testing&lt;/td&gt;
&lt;td&gt;Jest, Supertest&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Automation&lt;/td&gt;
&lt;td&gt;Keploy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Containerization&lt;/td&gt;
&lt;td&gt;Docker &amp;amp; Docker Compose&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;✨ Features&lt;br&gt;
✅ API Endpoints&lt;br&gt;
👥 Users&lt;br&gt;
GET /users – Get all users&lt;/p&gt;

&lt;p&gt;POST /users – Create a user&lt;/p&gt;

&lt;p&gt;PUT /users/:id – Update a user&lt;/p&gt;

&lt;p&gt;DELETE /users/:id – Delete a user&lt;/p&gt;

&lt;p&gt;📚 Books&lt;br&gt;
GET /api/books – Get all books&lt;/p&gt;

&lt;p&gt;POST /api/books – Add a book&lt;/p&gt;

&lt;p&gt;GET /api/books/:id – Get a book by ID&lt;/p&gt;

&lt;p&gt;DELETE /api/books/:id – Delete a book&lt;/p&gt;

&lt;p&gt;🧪 Testing Strategy&lt;br&gt;
My goal was to achieve 100% test coverage with the following layers:&lt;/p&gt;

&lt;p&gt;✅ Unit Tests – Test individual components&lt;/p&gt;

&lt;p&gt;✅ Integration Tests – Test DB operations&lt;/p&gt;

&lt;p&gt;✅ API Tests – Using Supertest&lt;/p&gt;

&lt;p&gt;✅ Auto-generated Tests – via Keploy&lt;/p&gt;

&lt;p&gt;🐰 How Keploy Helped&lt;br&gt;
I integrated Keploy CLI inside my Docker Compose setup. It captured real HTTP requests and database interactions and auto-generated test cases in the background!&lt;/p&gt;

&lt;p&gt;📦 Setup Command&lt;br&gt;
docker run -it --network="book-api-server_default" \&lt;br&gt;
-v "$(pwd)":/keploy -w /keploy \&lt;br&gt;
-e KEPLOY_MODE=record \&lt;br&gt;
-e KEPLOY_APP_HOST=node-app:5000 \&lt;br&gt;
-e KEPLOY_DB_DSN="postgres://postgres:#Anku265482@pgdb:5432/bookdb?sslmode=disable" \&lt;br&gt;
ghcr.io/keploy/keploy&lt;br&gt;
After hitting a few API routes with curl, Keploy generated test cases in keploy-tests/&lt;/p&gt;

&lt;p&gt;🧠 What I Learned&lt;br&gt;
Managing multi-container apps with Docker Compose&lt;/p&gt;

&lt;p&gt;Connecting Node.js with PostgreSQL in Docker&lt;/p&gt;

&lt;p&gt;Handling database connection errors inside Docker&lt;/p&gt;

&lt;p&gt;Writing clean, layered API architecture&lt;/p&gt;

&lt;p&gt;Using Keploy to record, replay, and test real API usage&lt;/p&gt;

&lt;p&gt;Solving tricky Git submodule and push errors&lt;/p&gt;

&lt;p&gt;📸 Screenshots&lt;br&gt;
✅ Test Coverage Report&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbr373dxrpwr3jx12vq91.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbr373dxrpwr3jx12vq91.png" alt="Image description" width="800" height="387"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🐰 Keploy CLI Output&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3q1ma2srmcv6x1taywxt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3q1ma2srmcv6x1taywxt.png" alt="Image description" width="800" height="383"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📂 Generated Keploy Test Files&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fzsxpwhdfhdzbx9o8mnx2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fzsxpwhdfhdzbx9o8mnx2.png" alt="Image description" width="800" height="267"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🐳 API Curl Request&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2vme25z9byror4zxog5j.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F2vme25z9byror4zxog5j.png" alt="Image description" width="800" height="108"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔗 Links&lt;br&gt;
GitHub Repo: &lt;a href="https://github.com/ankita-2311/book-api-server" rel="noopener noreferrer"&gt;https://github.com/ankita-2311/book-api-server&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💬 Feedback? Let’s connect on LinkedIn&lt;/p&gt;

&lt;p&gt;🏁 Final Words&lt;br&gt;
Keploy simplified testing for me — instead of writing boilerplate test cases, I just interacted with my API and let Keploy generate them. Highly recommended for any project with REST APIs!&lt;/p&gt;

&lt;p&gt;If you enjoyed reading or found this helpful, do share and tag @KeployIO. 💙&lt;/p&gt;

</description>
      <category>node</category>
      <category>testing</category>
      <category>docker</category>
      <category>api</category>
    </item>
  </channel>
</rss>
