<?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: Hari Gokul</title>
    <description>The latest articles on DEV Community by Hari Gokul (@hari_gokul_c67398029cbc70).</description>
    <link>https://dev.to/hari_gokul_c67398029cbc70</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%2F4143106%2F1aebbfd9-4b2b-46a2-93a1-7f611fe11892.png</url>
      <title>DEV Community: Hari Gokul</title>
      <link>https://dev.to/hari_gokul_c67398029cbc70</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hari_gokul_c67398029cbc70"/>
    <language>en</language>
    <item>
      <title>A Test Failed. How Do We Know Whether It's a Bug or an Automation Issue?</title>
      <dc:creator>Hari Gokul</dc:creator>
      <pubDate>Tue, 27 Oct 2026 14:31:45 +0000</pubDate>
      <link>https://dev.to/hari_gokul_c67398029cbc70/a-test-failed-how-do-we-know-whether-its-a-bug-or-an-automation-issue-1ain</link>
      <guid>https://dev.to/hari_gokul_c67398029cbc70/a-test-failed-how-do-we-know-whether-its-a-bug-or-an-automation-issue-1ain</guid>
      <description>&lt;p&gt;When I started exploring test automation, I thought a failed test usually meant something was wrong with the application.&lt;/p&gt;

&lt;p&gt;But I realized that isn't always true. Sometimes, the issue is in the automation script or the test environment.&lt;/p&gt;

&lt;p&gt;The real challenge is understanding why a test failed, not just that it failed.&lt;/p&gt;

&lt;p&gt;Imagine an automated test checks the login page of an online shopping application. It fails because it cannot find the Login button.&lt;/p&gt;

&lt;p&gt;Does that mean the application has a bug?&lt;/p&gt;

&lt;p&gt;Not necessarily. The button's locator might be outdated, the page might not have loaded completely, or the application itself might have an issue.&lt;/p&gt;

&lt;p&gt;Each possibility needs a different solution.&lt;/p&gt;

&lt;p&gt;A practical approach is to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Check the exact step where the test failed.&lt;/li&gt;
&lt;li&gt;Review logs, screenshots, and execution details.&lt;/li&gt;
&lt;li&gt;Reproduce the issue to understand whether it happens consistently.&lt;/li&gt;
&lt;li&gt;Compare the actual application behaviour with the expected result.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal isn't simply to make the test pass. It's to identify the actual cause and fix the right problem.&lt;/p&gt;

&lt;p&gt;While exploring AI-powered test automation, I came across X360 AI Tech.&lt;/p&gt;

&lt;p&gt;I found its focus on test execution details and failure analysis relevant to the problem I was exploring. These capabilities can help teams investigate failed tests and better understand what happened during execution.&lt;/p&gt;

&lt;p&gt;This also got me thinking about how AI could help distinguish between application bugs, automation issues, and environment-related failures. By analyzing execution evidence, identifying patterns, and suggesting possible causes, AI could help make debugging more efficient.&lt;/p&gt;

&lt;p&gt;However, these suggestions still need to be verified against actual evidence. AI can support the investigation, but understanding the root cause remains essential.&lt;/p&gt;

&lt;p&gt;I believe this is an important direction for test automation: moving beyond simply reporting failures towards understanding them.&lt;/p&gt;

&lt;p&gt;A failed test doesn't automatically mean there's an application bug. It's a signal to investigate.&lt;/p&gt;

&lt;p&gt;For me, the bigger opportunity in test automation is not just running tests faster, but helping teams understand failures and make better decisions.&lt;/p&gt;

&lt;p&gt;When a test fails in your project, what's the first thing you check to determine whether it's an application bug, an automation issue, or an environment problem?&lt;/p&gt;

</description>
      <category>softwaretesting</category>
      <category>testautomation</category>
      <category>ai</category>
      <category>debugging</category>
    </item>
    <item>
      <title>Before Test Automation Begins, It Starts With Requirements</title>
      <dc:creator>Hari Gokul</dc:creator>
      <pubDate>Fri, 23 Oct 2026 16:20:52 +0000</pubDate>
      <link>https://dev.to/hari_gokul_c67398029cbc70/before-test-automation-begins-it-starts-with-requirements-i2j</link>
      <guid>https://dev.to/hari_gokul_c67398029cbc70/before-test-automation-begins-it-starts-with-requirements-i2j</guid>
      <description>&lt;p&gt;In my previous post, I explored why test automation is about more than just writing scripts and running tests.&lt;/p&gt;

&lt;p&gt;As I continued exploring this topic, one question came to mind: What if good test automation actually starts before we write the first test?&lt;/p&gt;

&lt;p&gt;Why Do Requirements Matter?&lt;/p&gt;

&lt;p&gt;Imagine an online shopping app with a requirement that says users should be able to apply a discount coupon during checkout. Testing a valid coupon is easy enough. But what happens if the coupon has expired, the order value is too low, or the user enters an invalid code?&lt;/p&gt;

&lt;p&gt;A simple requirement can lead to several test scenarios.&lt;/p&gt;

&lt;p&gt;If we don't understand the expected behaviour clearly, we might miss important cases or create tests based on assumptions. This made me realise that writing more tests doesn't always mean better testing. First, we need to understand what should happen and what could go wrong.&lt;/p&gt;

&lt;p&gt;While exploring this area, I became to know about how AI could help turn requirements into meaningful test scenarios.&lt;/p&gt;

&lt;p&gt;AI can suggest test cases, identify possible edge cases, and help testers explore different situations. However, if the requirement itself is unclear, the generated scenarios may also be based on incorrect assumptions. That's why reviewing requirements and validating the suggested test cases remain important.&lt;/p&gt;

&lt;p&gt;While researching this connection between requirements and test automation, I came across X360 AI Tech.&lt;/p&gt;

&lt;p&gt;Its publicly described approach includes using product context and acceptance criteria to help generate structured test scenarios. I found this relevant to what I was exploring: how can we move from written requirements to useful test scenarios without missing the intended behaviour?&lt;/p&gt;

&lt;p&gt;It also made me think about how AI could help reduce repetitive work while allowing testers to focus more on understanding requirements and identifying potential risks.&lt;/p&gt;

&lt;p&gt;I'm beginning to see that effective test automation doesn't start with writing code. It starts with understanding what needs to be tested.&lt;/p&gt;

&lt;p&gt;AI can help along the way, but clear requirements, human judgement, and proper validation still matter.&lt;/p&gt;

&lt;p&gt;I'm continuing to explore this topic and would love to learn from others' experiences.&lt;/p&gt;

&lt;p&gt;When a requirement isn't clear enough to write a test case, how do you usually handle it?&lt;/p&gt;

</description>
      <category>testing</category>
      <category>automation</category>
      <category>ai</category>
      <category>softwaretesting</category>
    </item>
    <item>
      <title>Exploring End-to-End Test Automation: More Than Just Execution</title>
      <dc:creator>Hari Gokul</dc:creator>
      <pubDate>Fri, 16 Oct 2026 10:08:45 +0000</pubDate>
      <link>https://dev.to/hari_gokul_c67398029cbc70/exploring-end-to-end-test-automation-more-than-just-execution-nkc</link>
      <guid>https://dev.to/hari_gokul_c67398029cbc70/exploring-end-to-end-test-automation-more-than-just-execution-nkc</guid>
      <description>&lt;p&gt;When we talk about test automation, the first thing that often comes to mind is writing scripts and running tests. But is test automation really just about that?&lt;/p&gt;

&lt;p&gt;As I've been exploring this field, I've started looking at testing from a broader perspective. Writing a test is one part of the process. Understanding what to test, making sure the test is reliable, investigating failures, and keeping tests useful as an application changes are equally important.&lt;/p&gt;

&lt;p&gt;In this post, I want to share some of my thoughts on end-to-end test automation, how AI is becoming part of it, and what I'm interested in learning more about.&lt;/p&gt;

&lt;p&gt;What Is End-to-End Test Automation?&lt;/p&gt;

&lt;p&gt;Imagine you're using an online shopping application. You log in, search for a product, add it to your cart, complete the payment, and receive an order confirmation. For everything to work correctly, several parts of the application need to work together. End-to-end (E2E) testing checks whether this complete user journey works as expected.&lt;/p&gt;

&lt;p&gt;Instead of checking just one button or one function, we test how different parts of an application work together from the user's point of view.&lt;/p&gt;

&lt;p&gt;As I've been exploring this field, I came across X360 AI Tech, a platform focused on AI-powered test automation.&lt;/p&gt;

&lt;p&gt;What I found was its broader approach to the testing workflow. The platform's publicly described capabilities cover areas such as requirement ingestion, test scenario generation, coverage intelligence, automated execution, self-healing, and failure analysis.&lt;/p&gt;

&lt;p&gt;Exploring platforms like this gives me more questions to investigate. I find this direction interesting because it shifts the discussion from simply automating test execution to considering how the overall testing process might be improved.&lt;/p&gt;

&lt;p&gt;For me, exploring these questions is a useful way to understand where modern test automation is heading.&lt;/p&gt;

&lt;p&gt;I don't expect one tool or technique to solve every testing challenge. Different applications have different requirements, risks, and constraints. Understanding those differences is part of what makes exploring this field interesting.&lt;/p&gt;

&lt;p&gt;I plan to continue exploring these ideas and sharing what I learn along the way.&lt;/p&gt;

&lt;p&gt;I'm interested in learning from your experiences and perspectives.&lt;/p&gt;

&lt;p&gt;This is part of my ongoing exploration of modern test automation. More learning and questions to come!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>testing</category>
      <category>learning</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
