Back/Engineering/ChatGPT
IntermediateEngineering

Automate Web App QA Testing with AI Browser Automation

Run browser-based QA across primary and adversarial paths, producing reproducible bugs instead of a vague test summary.

Automate Web App QA Testing with AI Browser Automation

06:51 to 12:26: Claire uses Codex browser automation to exercise a web app beyond the happy path and return a detailed record of the tested flows and failures.

Before you start

What you need

  • A test environment and seeded accounts
  • Named user journeys and role boundaries
  • Expected behavior and stop conditions

What you’ll make

A QA report with passed paths, reproducible failures, screenshots, and affected environment details.

Tools used

Step by step

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

5 steps

Step01

Install AI Desktop App and Extension

Download and install an AI desktop app with browser control, such as the ChatGPT or Claude desktop app. You will also need its corresponding Chrome extension to allow the AI to see and control your browser.

Example prompt
Install the approved desktop app and browser extension, then confirm the test profile and environment.
Step02

Open Your Web App

Open the web application you want to test in the AI app's browser. This can be a live URL or a local development environment running on your machine.

Example prompt
Open [test URL], sign in as [role], and confirm the seeded records are present.
Step03

Prompt the AI for Testing

Instruct the AI to test the application using a directive prompt. Specify the user flow to test, the criteria to evaluate, such as usability and mobile responsiveness, and the desired output format for the bug report.

Example prompt
Test these journeys: [list]. Include happy, invalid, empty, repeated, mobile, and permission cases. Do not perform destructive production actions.
Step04

Monitor AI Execution

Watch as the AI agent navigates your site. It will methodically click buttons, test failure states like submitting a form with a required field left blank, and change viewport sizes to simulate different devices.

Example prompt
Record each action, screenshot failures, and stop if authentication or environment differs from the brief.
Step05

Review the Bug Report

Review the bug report generated by the AI. A typical output is a spreadsheet that lists each issue with a description, steps to reproduce, and the corresponding screenshot for context.

Example prompt
Return a bug table with severity, URL, role, data, steps, expected, actual, and evidence, plus passed checks.

What good looks like

  • Every bug includes steps, expected result, actual result, and evidence
  • The run covers happy, error, empty, and permission states
  • Testing avoids destructive production actions

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

After the steps

Runbook notes

How to recover when the loop fails and where human judgment helps.

Recover

If it goes sideways

The agent tests only the happy path
Name adversarial, empty, repeated, and permission cases explicitly.
A failure cannot be reproduced
Record account, data, URL, time, and exact steps at discovery.
Automation risks changing real data
Use a test environment and prohibit destructive actions.

Start shipping
better products.

Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start
No credit card
SOC 2 certified
Enterprise ready