Mastering Automatability for Test Automation

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