BAM logo blackBAM logo white

Menu

© 2026 Blaise Moses
ActiveLast updated: Mar 2026

Agentic Playwright Team

A multi-agent testing proof of concept for systematic exploration, rapid scripting, and scalable browser automation workflows.

AI & AutomationTestingPersonal

Stack: Playwright · Agent Browser · Claude Code · TypeScript

Progress65%

Role

POC designer and builder

Stage

Active prototype

Primary focus

Exploration and script acceleration

Target use

Internal QA and enterprise scaling

Overview

This project started as a proof of concept for using agentic workflows to explore applications, reason about what should be tested, and speed up the first draft of Playwright coverage.

I used it to pressure-test whether multi-agent coordination could improve browser testing throughput without losing the discipline required for reliable automation.

I am working on the base idea I proved here now, and have also been playing around with deployed solutions to use my agent team to automatically test and document QA process for my personal webapps and projects.

Goals and Architecture

  • Combine browser automation with agent-guided exploration so the system can inspect an app before writing tests.
  • Keep Playwright as the deterministic execution layer while agents handle discovery, planning, and candidate script generation.
  • Make the workflow useful as both a personal accelerator and a foundation for more structured enterprise experimentation.

Current Work and Learnings

  • Tightening the handoff between exploration output and durable test artifacts so generated coverage is easier to keep and maintain.
  • Refining prompt and role boundaries to reduce redundant work across agents and keep the process auditable.
  • Validating where this approach adds real leverage versus where traditional authored automation is still the better fit.