This podcast episode is a chat with Dragan Spiridonov who created the Agentic QE fleet. Agentic AI for Quality Engineering. It can work with code, or websites. We will explore Agentic AI, what it means, and how to use it to improve your Software Development and Testing. Also introduce the Agentic QE Fleet and how it augments Claude Code and Claude Flow.

We cover:

- Introduce Dragan Spiridonov and his work

- Introduce Agent Based Testing and Development

- Introduce and explain Agentic QE tooling

- Explain difference between Agentic QE tooling and Base Claude

- How has working on this changed Dragan's view of his skillsets and role

- How to learn: AI, Agentic AI, Agentic QE?

- Lessons learned from building and using AI that we can apply to any AI tooling

- Future of Agentic QE Tooling

- Future of AI in Testing and Development

Links:

- https://forge-quality.dev/

- https://www.linkedin.com/in/dragan-spiridonov/

- https://spiridonovdragan.com/

- https://agentic-qe.dev/

- Overview of Agentic Quality Engineering Fleet: Revolutionizing Software Testing with AI Agents https://video.agentics.org/media/t/1_htfe35tu/370465892

- https://quantum-qe.dev/

- https://github.com/proffesor-for-testing/agentic-qe

- https://github.com/ruvnet/claude-flow

- https://agentics.org/

- for video archive https://video.agentics.org

Based on my experience with AI, am I optimistic or pessimistic. I gain huge value from AI during development, but have I managed the same in Testing? And how will the Tester role change, what do we need to do to adapt? I look forward to learning more and describe my next steps.

00:00 - Introduction: Am I an AI Optimist or Pessimist?

02:16 - AI, Jobs, and Management Excuses

06:33 - How AI Changes Our Roles

10:49 - Human Connection vs. AI: Where I Refuse to Use It

16:27 - Building and Using AI Tools for Programming

22:46 - Automation, Testing, and the Human Factor

28:21 - The Future: Agentic AI, Fundamentals, and Looking Forward

The answers given during a Browserstack Community AMA session held on Discord on the 11th of December 2025, following a live LinkedIn video stream. The session focused on "Mastering Automatability for Test Automation". The main theme is the concept of Automatability, which I view as the ability to automate, this personal skill is more critical than reliance on specific tools. The discussion covers various topics, including how to separate automation problems from application design issues, dealing with slow UIs and non-automation friendly third-party widgets, evaluating automation readiness, and addressing common architectural failings related to large-scale UI automation.

00:00:00 Introduction

00:01:27 key early lesson about automatability?

00:01:56 separating automation issues vs. design issues?

00:03:49 is slow UI a testability or automatability problem?

00:06:50 handling non-automatable third-party widgets?

00:09:20 assessing automation readiness - any framework?

00:11:23 common architectural patterns that break at scale?

00:13:37 prioritizing testability vs. automation in sprints?

00:16:51 do modern tools reduce the need for good design?

00:19:32 explaining automatability as an investment?

00:21:44 how do AI agents handle dynamic/third-party elements?

00:23:17 early signs a feature will be flaky when automated?

00:26:10 which microservice layers to automate first?

00:29:16 high-ROI automatability fixes for small budgets?

00:30:55 early dev–test collaboration to prevent rework?

00:34:08 thinking about automatability in continuous delivery?

Join the BrowserStack Discord community and discover more AMA sessions https://www.browserstack.com/community