heal-dev/heal-playwright-tracer — Open-source statement-level Playwright tracer, purpose-built for AI agents.

Description and use

**Brief Summary**
heal‑dev/heal‑playwright‑tracer is an open‑source, statement‑level tracer built on top of Playwright that captures fine‑grained execution data for UI tests. Designed for AI agents, it delivers more accurate test‑run analysis and can be used to automate repetitive QA steps, glue together tooling, and schedule operational tasks.

**Value**

• **Automation of manual QA work** – By instrumenting every Playwright command, the tracer produces a rich execution graph that AI agents can consume to generate insights, self‑heal flaky tests, or drive downstream workflows.
• **Repeatable, observable pipelines** – The captured telemetry can be fed into CI/CD, monitoring dashboards, or custom bots, turning ad‑hoc test runs into repeatable, observable processes.
• **Rapid integration for prototyping** – With a modest API surface and a single‑file npm install, teams can quickly replace their existing Playwright runner with the tracer to start collecting data without rewriting tests.

**Practical Adoption Path**

1. **Proof‑of‑concept** – Clone the repo, run npm install heal-playwright-tracer and follow the README to wrap the existing Playwright test harness. Verify that trace files are generated for a small subset of tests.
2. **Toolchain hookup** – Connect the output (JSON/NDJSON traces) to the AI component or observability platform you intend to use (e.g., LangChain agents, Grafana, custom dashboards).
3. **Iterative expansion** – Gradually migrate more test suites, adding custom annotations where needed. Because the tracer is a thin wrapper, existing Playwright tests remain unchanged.
4. **Stability & maintenance review** – Audit the dependency tree, lock versions, and add health‑checks to the CI pipeline to ensure the tracer does not introduce runtime regressions.

**Production Readiness**

• **Maturity**: Medium. The project has 35 stars, recent activity (last commit 2026‑05‑11), and a clear JavaScript codebase, making it suitable for internal prototypes or low‑risk production workloads.
• **Readiness Checklist**
• ✅ Verify compatibility with your Playwright version.
• ✅ Pin the tracer’s version and run a dependency audit (e.g., npm audit).
• ✅ Add monitoring for trace generation failures and fallback to standard Playwright runs.
• ✅ Conduct a small load test to gauge any performance overhead (typically a few milliseconds per command).
• **Risks** – The integration guidance is sparse; you’ll need to invest time in understanding the trace format and wiring it to downstream AI/observability tools. A controlled pilot is recommended before a full rollout.

In short, heal‑playwright‑tracer can eliminate repetitive manual QA steps and enable AI‑driven test analytics, but teams should start with a limited proof‑of‑concept, validate the integration effort, and perform the usual production hardening before relying on it in mission‑critical pipelines.

Problem

heal-dev/heal-playwright-tracer helps remove repetitive manual operations from a workflow.

Outcome

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.

Workflow

• remove manual work
• connect tools into repeatable flows
• schedule operational tasks

Evidence

Open-source statement-level Playwright tracer, purpose-built for AI agents. Analyzes test runs with increased accuracy.

Source