# Browser Automation Browser automation is the programmatic remote control of web browsers, commonly used by developers and testers to automate browser-based tests and tooling. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Product Engineering for PMs, Part 1: Build a SaaS App Without Coding DevFeed: [Product Engineering for PMs, Part 1: Build a SaaS App Without Coding]() Original publisher: [Read original article]() Author: Paweł Huryn Published: 2026-08-31T15:35:45Z Content type: tutorial Language: en Sources: [The Product Compass]() Topics: [Software as a service](), [Claude Code](), [Supabase](), [Browser Automation](), [Automation](), [test](), [coding](), [Artificial Intelligence]() Tags: [automation](), [browser](), [build](), [claude](), [claude-code](), [coding](), [deploy](), [how-to](), [monetization](), [saas]() ### AI overview A step-by-step series for PMs and non-coders to design, build, secure, deploy, launch, monetize, analyze, and monitor a commercial SaaS app using Claude Code, Clerk, and Supabase. The case study is AskOne, a live Q&A product, and the article includes prompts, templates, browser automation, and testing workflows. ### Source excerpt Design, build, secure, and deploy a real multi-tenant SaaS app in 3-4 hours: Claude Code, Clerk, Supabase. No coding. All prompts included. ## Browser automation with Pydantic AI + Playwright DevFeed: [Browser automation with Pydantic AI + Playwright]() Original publisher: [Read original article]() Author: Pamela Fox (noreply@blogger.com) Published: 2026-08-20T21:57:18Z Content type: tutorial Language: en Sources: [Pamela Fox]() Topics: [Playwright](), [Pydantic](), [Browser Automation](), [Artificial Intelligence](), [Azure OpenAI](), [Entra ID](), [Authentication](), [OAuth 2.0](), [OpenTelemetry]() Tags: [agents](), [ai](), [api-keys](), [authentication](), [automation](), [azure-openai](), [browser](), [microsoft](), [microsoft-foundry](), [openai](), [playwright](), [python]() ### AI overview This tutorial explains how to combine Pydantic AI with Playwright to build agents that browse websites programmatically. It covers connecting Pydantic AI to Microsoft Foundry models through an OpenAI-compatible endpoint, using Entra token-based authentication, and applying Playwright for browsing, manual QA, and design iteration. ### Source excerpt When we build agents, we often want to give them the ability to browse the web: open webpages, navigate from one page to the other, and read the content of a webpage. By combining Pydantic AI with the Playwright capability from Pydantic AI Harness, we can build agents that browse the web safely and programmatically. Using Pydantic AI with Microsoft Foundry models Pydantic AI is an open-source model-agnostic framework from Pydantic for building LLM-based applications and agents. It's type-safe and supports OpenTelemetry, making it a great choice for robust production applications. We can use Pydantic-AI with Microsoft Foundry models using either API keys or Entra token-based authentication. When possible, we always recommend the keyless route, so that's what we'll demonstrate here. We use the azure-identity package to authenticate with Entra, using either local or managed identity, and get back a token provider callback function for that credential: from azure.identity.aio import AzureDeveloperCliCredential, get_bearer_token_provider credential = AzureDeveloperCliCredential() token_provider = get_bearer_token_provider(credential, "https://cognitiveservices.azure.com/.default") Then we use the OpenAI package to configure the model connection: from openai import AsyncOpenAI client = AsyncOpenAI( base_url=os.environ["AZURE_OPENAI_ENDPOINT"] + "/openai/v1", api_key=token_provider, ) model = OpenAIChatModel( model_name=os.environ["AZURE_OPENAI_CHAT_DEPLOYMENT"], provider=OpenAIProvider(openai_client=client), ) Let's explain the options used above: base_url: We point this at the OpenAI-compatible endpoint for our Foundry model. This endpoint works for Azure OpenAI models (like gpt-5.4, which this project deploys), and for cross-provider Foundry models that support the OpenAI v1 API, like Kimi-K2.7-Code. The base URL looks like "https://AZURE_OPENAI_SERVICE_NAME.openai.azure.com/openai/v1". api_key: We pass in the token provider callback function that generates OAuth2 token ## The unbreakable web: From fragile scripts to bulletproof Workflows DevFeed: [The unbreakable web: From fragile scripts to bulletproof Workflows]() Original publisher: [Read original article]() Author: Kyle Jeong Published: 2025-08-20T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Browser Automation](), [Automation](), [Artificial Intelligence](), [AI Bots]() Tags: [agents](), [ai-agents](), [announcements](), [automation](), [browser](), [execution](), [self-healing](), [workflows]() ### AI overview The article argues that production web automation needs more than brittle scripts. It presents Browserbase's Stagehand SDK and Temporal Durable Execution as a combination for semantic interaction with web elements, recovery from failures, and continuation after interruptions. ### Source excerpt Build bulletproof browser automation and AI agents with Browserbase and Temporal. Stagehand and Durable Execution turn fragile scripts into resilient Workflows. ## Improved Browser Testing on Heroku with Chrome DevFeed: [Improved Browser Testing on Heroku with Chrome]() Original publisher: [Read original article]() Author: Mars Hall Published: 2024-04-09T22:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Browser Automation](), [Chrome](), [Testing](), [CI/CD](), [Continuous Delivery (CD)]() Tags: [automated](), [browser](), [buildpacks](), [chrome](), [ci](), [continuous-delivery](), [continuous-integration](), [developer-tools](), [engineering](), [heroku](), [security](), [testing](), [tests]() ### AI overview Heroku introduces the Chrome for Testing Heroku Buildpack, a community buildpack designed to improve installation reliability for automated browser testing in Heroku apps. It addresses Chrome and Chromedriver version mismatches by keeping their versions aligned for testing environments. ### Source excerpt For developers and businesses offering a web-based product, automated browser testing is a critical tool to ensure continuous delivery of a reliable service. Developers write browser tests by scripting actions against a real browser, simulating real usage by navigating, selecting, and making assertions about web pages and their document elements. In this post, we introduce [...] The post Improved Browser Testing on Heroku with Chrome appeared first on Heroku. ## Updating to .NET 8, updating to IHostBuilder, and running Playwright Tests within NUnit headless or headed on any OS DevFeed: [Updating to .NET 8, updating to IHostBuilder, and running Playwright Tests within NUnit headless or headed on any OS]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2024-03-07T01:12:13Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [Playwright](), [.NET](), [Testing](), [Browser Automation](), [Integration testing](), [ASP.NET](), [Selenium](), [GitHub Actions]() Tags: [asp-net](), [automation-testing](), [browser](), [ci-cd](), [debug](), [devops](), [dotnetcore](), [integration](), [linux](), [net](), [playwright](), [selenium](), [testing](), [tests](), [unit-testing](), [visual-studio](), [vs-code](), [web](), [windows]() ### AI overview A tutorial on updating a .NET application to .NET 8 and running Playwright browser tests through NUnit. It explains the transition from IWebHostBuilder to IHostBuilder and describes cross-platform, headless or headed testing across local systems, containers, and CI environments. ### Source excerpt I've been doing not just Unit Testing for my sites but full on Integration Testing and Browser Automation Testing as early as 2007 with Selenium. Lately, however, I've been using the faster and generally more compatible Playwright. It has one API and can test on Windows, Linux, Mac, locally, in a container (headless), in my CI/CD pipeline, on Azure DevOps, or in GitHub Actions. For me, it's that last moment of truth to make sure that the site runs completely from end to end. I can write those Playwright tests in something like TypeScript, and I could launch them with node, but I like running end unit tests and using that test runner and test harness as my jumping off point for my .NET applications. I'm used to right clicking and "run unit tests" or even better, right click and "debug unit tests" in Visual Studio or VS Code. This gets me the benefit of all of the assertions of a full unit testing framework, and all the benefits of using something like Playwright to automate my browser. In 2018 I was using WebApplicationFactory and some tricky hacks to basically spin up ASP.NET within .NET (at the time) Core 2.1 within the unit tests and then launching Selenium. This was kind of janky and would require to manually start a separate process and manage its life cycle. However, I kept on with this hack for a number of years basically trying to get the Kestrel Web Server to spin up inside of my unit tests. I've recently upgraded my main site and podcast site to .NET 8. Keep in mind that I've been moving my websites forward from early early versions of .NET to the most recent versions. The blog is happily running on Linux in a container on .NET 8, but its original code started in 2002 on .NET 1.1. Now that I'm on .NET 8, I scandalously discovered (as my unit tests stopped working) that the rest of the world had moved from IWebHostBuilder to IHostBuilder five version of .NET ago. Gulp. Say what you will, but the backward compatibility is impressive. As such my code for Progr ## Dockerized e2e tests DevFeed: [Dockerized e2e tests]() Original publisher: [Read original article]() Published: 2018-02-15T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Docker](), [Selenium](), [Browser Automation](), [CI/CD](), [Testing](), [Travis CI](), [webDriver](), [Chrome](), [Firefox]() Tags: [browser](), [ci](), [containers](), [docker](), [firefox](), [selenium](), [testing](), [travis-ci](), [webdriver]() ### AI overview This tutorial explains how to run Selenium end-to-end tests in Docker and integrate them with CI tools such as Travis CI, GitLab CI, or Jenkins. It describes using Selenium Hub and Chrome and Firefox node containers, configuring WebdriverIO, capturing screenshots for failed tests, and organizing tests with a Page Object. ### Source excerpt In my free time, I'm trying to learn something new and best of way learning is by doing. To avoid spinning my wheels in vain I'm helping to develop some product. In the previous post, I've described what we've decided to use for the UI and pointed out that I'm going to write integration tests. Here is how I integrated selenium e2e tests with gitlab-ci/travis-ci/whatever by running them in docker. Read more ## Element interactability checks with geckodriver and Firefox 58 DevFeed: [Element interactability checks with geckodriver and Firefox 58]() Original publisher: [Read original article]() Author: Henrik Skupin Published: 2017-12-15T12:59:55Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Selenium](), [Browser Automation](), [webDriver](), [Firefox]() Tags: [automation](), [firefox](), [geckodriver](), [marionette](), [mozilla](), [selenium](), [software](), [test](), [testing](), [tests](), [webdriver]() ### AI overview Firefox 58 enables interactability checks by default for Selenium and geckodriver Element Click and Element Send Keys operations. The article explains the resulting not-interactable errors, how to report false positives, and the temporary moz:webdriverClick workaround. ### Source excerpt When you are using Selenium and geckodriver to automate your tests in Firefox you might see a behavior change with Firefox 58 when using the commands Element Click or Element Send Keys. For both commands we have enabled the interactability checks by default now. That means that if such an operation has to be performed for any kind of element it will be checked first, if a click on it or sending keys to it would work from a normal user perspective at all. If not a not-interactable error willContinue readingElement interactability checks with geckodriver and Firefox 58 ## Using Selenium and webdriver to interact with insecure SSL pages in Firefox DevFeed: [Using Selenium and webdriver to interact with insecure SSL pages in Firefox]() Original publisher: [Read original article]() Author: Admin Published: 2017-01-23T14:13:56Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Selenium](), [Browser Automation](), [SSL](), [webDriver](), [Python]() Tags: [automation](), [firefox](), [marionette](), [mozilla](), [mozqa](), [python](), [selenium](), [ssl](), [test](), [testing](), [webdriver]() ### AI overview This tutorial explains how to use Selenium and Firefox WebDriver to access pages with invalid or self-signed SSL certificates during automated tests. It describes the Firefox 52 and Selenium 3 requirements and shows how to enable insecure certificate acceptance with the acceptInsecureCerts capability. ### Source excerpt Interacting with insecure SSL pages (eg. self-signed) in an automated test written for Selenium is an important feature. Especially when tests are getting run against locally served test pages. Under those circumstances you might never get fully secured websites served to the browser instance under test. To still allow running your tests with a successful test result, Selenium can instruct the browser to ignore the validity check, which will simply browse to the specified site without bringing up the SSL error page. Since the default driver for Firefox was switchedContinue readingUsing Selenium and webdriver to interact with insecure SSL pages in Firefox ## Marionette, Act II: Harnessing automation to test the browser DevFeed: [Marionette, Act II: Harnessing automation to test the browser]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-22T00:00:00Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [Browser Automation](), [Testing](), [Firefox](), [Mozilla](), [Python](), [API]() Tags: [api](), [automation](), [browser](), [firefox](), [marionette](), [mozilla](), [python](), [test]() ### AI overview This article explains the Marionette test harness, a testing framework for running automated tests on Mozilla browsers using the Marionette automation tools. It describes how browser automation supports testing instead of manual checks, with a Python API controlling the Gecko browser engine. ### Source excerpt Welcome back to my post series on the Marionette project! In Act I, we looked into Marionette's automation framework for Gecko, the engine behind the Firefox browser. Here in Act II, we'll take a look at a complementary side of the Marionette project: the testing framework that helps us run tests using our Marionette-animated browser, aka the Marionette test harness. If - like me at the start of my Outreachy internship - you're clueless about test harnesses, or the Marionette harness in particular, and want to fix that, you're in the right place! Wait, what's Marionette again? Quick recap from Act I: Marionette refers to a suite of tools for automated testing of Mozilla browsers. In that post, we saw how the Marionette automation framework lets us control the Gecko browser engine (our "puppet"), thanks to a server component built into Gecko (the puppet's "strings") and a client component (a "handle" for the puppeteer) that gives us a simple Python API to talk to the server and thus control the browser. But why do we need to automate the browser in the first place? What good does it do us? Well, one thing it's great for is testing. Indulge me in a brief return to my puppet metaphor from last time, won't you? If the automation side of Marionette gives us strings and a handle that turn the browser into our puppet, the testing side of Marionette gives that puppet a reason for being, by letting it perform: it sets up a stage for the puppet to dance on, tell it to carry out a given performance, write a review of that performance, and tear down the stage again. OK, OK, metaphor-indulgence over; let's get real. Wait, why do we need automated browser testing again? As Firefox1 contributors, we don't want to have to manually open up Firefox, click around, and check that everything works every time we change a line of code. We're developers, we're lazy! Clueless via POPSUGAR But we can't not do it, because then we might not realize that we've broken the entire internet (or, yo ## Understanding WebDriver, Selenium, Marionette, and Browser Automation DevFeed: [Understanding WebDriver, Selenium, Marionette, and Browser Automation]() Original publisher: [Read original article]() Author: Maja Frydrychowicz Published: 2016-07-12T04:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [webDriver](), [Browser Automation](), [Selenium](), [Testing](), [Firefox](), [HTTP](), [JSON](), [Mozilla](), [JavaScript](), [Open Source]() Tags: [automation](), [browser](), [browser-ui](), [browsers](), [client-driver](), [firefox](), [foss](), [geckodriver](), [harness](), [http](), [javascript](), [json](), [marionette](), [mozilla](), [open-source](), [payload](), [request](), [responses](), [selenium](), [w3c](), [web](), [webdriver]() ### AI overview An explanatory article untangles the terminology around Marionette, Selenium, WebDriver, FirefoxDriver, and geckodriver. It explains the W3C WebDriver Specification and how its browser-agnostic protocol uses JSON over HTTP to send commands and receive responses for browser automation and testing. ### Source excerpt I define WebDriver, W3C WebDriver, Selenium, geckodriver, FirefoxDriver, Marionette harness/runner/client/driver and more. ## Automate your UI testing with Nightwatch DevFeed: [Automate your UI testing with Nightwatch]() Original publisher: [Read original article]() Published: 2014-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Testing](), [Browser Automation](), [Front end](), [Selenium](), [webDriver](), [npm]() Tags: [automated](), [backend](), [front-end](), [npm](), [selenium](), [testing](), [ui-testing](), [webdriver]() ### AI overview A tutorial describing how to automate front-end UI tests with Nightwatch, Node, npm, and Selenium. It demonstrates a test that logs into a portal and verifies that web applications respond as expected, and explains the setup, test modules, runner configuration, and WebDriver communication. ### Source excerpt Lorem ipsum dolor sit amet