<?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>Forem: Mohammad Adnan</title>
    <description>The latest articles on Forem by Mohammad Adnan (@iamadnank9).</description>
    <link>https://forem.com/iamadnank9</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%2F3856477%2F5b0f813e-96ea-4527-8fce-87ef33bb2b0f.png</url>
      <title>Forem: Mohammad Adnan</title>
      <link>https://forem.com/iamadnank9</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/iamadnank9"/>
    <language>en</language>
    <item>
      <title>How I Started Using AI Agents for End-to-End Testing (Autonoma AI)</title>
      <dc:creator>Mohammad Adnan</dc:creator>
      <pubDate>Wed, 01 Apr 2026 23:03:45 +0000</pubDate>
      <link>https://forem.com/iamadnank9/how-i-started-using-ai-agents-for-end-to-end-testing-autonoma-ai-2dpj</link>
      <guid>https://forem.com/iamadnank9/how-i-started-using-ai-agents-for-end-to-end-testing-autonoma-ai-2dpj</guid>
      <description>&lt;p&gt;I’ve been thinking a lot about how broken testing workflows feel right now.&lt;/p&gt;

&lt;p&gt;Most of the time, writing end-to-end tests is slow, brittle, and honestly kind of painful. You write selectors, they break when the UI changes, and suddenly half your tests are useless.&lt;/p&gt;

&lt;p&gt;Recently, I came across Autonoma AI, and it feels like a completely different approach.&lt;/p&gt;

&lt;p&gt;Instead of writing test scripts, you just describe what you want in plain English.&lt;/p&gt;

&lt;p&gt;Something like:&lt;br&gt;
“Open the login page, enter credentials, and verify the dashboard loads.”&lt;/p&gt;

&lt;p&gt;And that’s it.&lt;/p&gt;

&lt;p&gt;Autonoma handles:&lt;/p&gt;

&lt;p&gt;Running tests on real browsers and devices&lt;br&gt;
Detecting elements using AI instead of fragile selectors&lt;br&gt;
Automatically fixing tests when UI changes (self-healing)&lt;/p&gt;

&lt;p&gt;That last part is huge. Anyone who’s worked with tools like Selenium or Cypress knows how annoying broken selectors can be.&lt;/p&gt;

&lt;p&gt;What’s interesting is that this isn’t just a testing tool — it feels like part of a bigger shift toward LLM-native development.&lt;/p&gt;

&lt;p&gt;Instead of writing code for everything, we’re starting to describe intent and let AI handle execution.&lt;/p&gt;

&lt;p&gt;I can see this being useful for:&lt;/p&gt;

&lt;p&gt;Startups that don’t want to maintain complex QA pipelines&lt;br&gt;
Teams shipping fast where UI changes constantly&lt;br&gt;
Solo devs who just want basic coverage without overhead&lt;/p&gt;

&lt;p&gt;I haven’t fully integrated it into a production project yet, but even the idea of replacing brittle tests with something adaptive is pretty exciting.&lt;/p&gt;

&lt;p&gt;Curious to see how this evolves.&lt;/p&gt;

&lt;p&gt;Repo:&lt;br&gt;
&lt;a href="https://github.com/autonoma-ai/autonoma" rel="noopener noreferrer"&gt;https://github.com/autonoma-ai/autonoma&lt;/a&gt;&lt;/p&gt;

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