<?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: Kabir Hossain</title>
    <description>The latest articles on DEV Community by Kabir Hossain (@prantomomo).</description>
    <link>https://dev.to/prantomomo</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%2F1391841%2Ffef3bc4e-398f-4fde-b098-798feb773be9.png</url>
      <title>DEV Community: Kabir Hossain</title>
      <link>https://dev.to/prantomomo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prantomomo"/>
    <language>en</language>
    <item>
      <title>My QA Automation Journey: From Zero to CI/CD 🚀</title>
      <dc:creator>Kabir Hossain</dc:creator>
      <pubDate>Mon, 21 Sep 2026 22:43:34 +0000</pubDate>
      <link>https://dev.to/prantomomo/my-qa-automation-journey-from-zero-to-cicd-3fdl</link>
      <guid>https://dev.to/prantomomo/my-qa-automation-journey-from-zero-to-cicd-3fdl</guid>
      <description>&lt;p&gt;Hello, &lt;br&gt;
I am embarking on a long journey into QA automation—and documenting my experiences along the way.&lt;br&gt;
Just a few months ago, while I could run &lt;code&gt;pytest&lt;/code&gt;, I lacked a clear understanding of what a professional automation framework actually looks like.&lt;br&gt;
I was familiar with some basic concepts of Python and automation. However, there was a significant gap between knowing isolated tools and understanding how everything integrates within a real-world QA engineering workflow.&lt;br&gt;
So, I decided to bridge that gap through hands-on practice.&lt;br&gt;
I am following a roadmap comprising over 200 practical, hands-on projects. It begins with Python and Playwright, progressing through CI/CD, observability, and AI-assisted testing, ultimately leading to the creation of an AI-driven QA platform.&lt;br&gt;
Here is what I have worked on so far:&lt;br&gt;
✅ Python Fundamentals&lt;br&gt;
✅ Playwright&lt;br&gt;
✅ Pytest&lt;br&gt;
✅ Page Object Model&lt;br&gt;
✅ API Testing&lt;br&gt;
✅ Authentication and Session Handling&lt;br&gt;
✅ Network Interception&lt;br&gt;
✅ Screenshots, Traces, Videos, and HTML Reports&lt;br&gt;
✅ GitHub Actions and CI/CD&lt;/p&gt;

&lt;p&gt;I am currently approaching Project 152 (P152).&lt;br&gt;
Through this process, I have realized something important: learning QA automation isn't just about learning how to write a test.&lt;br&gt;
It is equally crucial to understand what happens when a test fails. For instance, I recently set up a CI 'quality gate' for a project where the process went like this:&lt;/p&gt;

&lt;p&gt;Tests fail&lt;br&gt;
↓&lt;br&gt;
CI pipeline fails&lt;br&gt;
↓&lt;br&gt;
Evidence or data regarding the failure is collected&lt;br&gt;
↓&lt;br&gt;
Artifacts are uploaded&lt;/p&gt;

&lt;p&gt;If a test fails, the pipeline should fail too—but I didn't want the evidence or data concerning that failure to be lost along with the pipeline itself.&lt;br&gt;
It was a small project, certainly, but it taught me a valuable lesson about how a real-world CI pipeline should function.&lt;br&gt;
Throughout this journey, I will continue to document my project, mistakes, problem-solving approaches, and everything new I learn.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>cicd</category>
      <category>python</category>
      <category>testing</category>
    </item>
  </channel>
</rss>
