Agentic testing with Playwright: how AI agents plan, write and repair tests
How AI agents do QA work with Playwright today: the loop, the tools (test agents, MCP, Agent SDK), where agents go wrong and the guardrails that work.
Blog
Practical guides for teams that ship without a QA department. Templates you can copy, tools compared on what they actually do, and how we run QA with Claude agents and a human QA engineer.
New posts by RSS.
How AI agents do QA work with Playwright today: the loop, the tools (test agents, MCP, Agent SDK), where agents go wrong and the guardrails that work.
What self-healing tests really change, which AI fixes are safe, which need a person, and a review workflow, with a before/after Playwright example.
A field guide to flaky tests in Playwright: what causes them, how to find them with repeats, retries and traces, how to fix each cause, and how to quarantine safely.
Playwright API testing in practice: when API tests beat UI tests, the request fixture, a create to delete example with cleanup, faster UI setup and token auth.
A complete Playwright GitHub Actions workflow to copy: sharding, merged HTML reports, retries with traces, secrets for test accounts and what not to cache.
Maestro vs Appium vs Mobilewright, compared from their official docs: how tests are written, iOS and Android support, setup, CI, device clouds and licenses.
A Go/No-Go checklist for software releases: the criteria that matter, who makes the call, examples of No-Go conditions and a template to paste into your release ticket.
A regression testing checklist for small teams: what to retest before each release, layer by layer, how to keep the suite small and trusted, and a template to copy.
A bug report template with a filled example, a GitHub issue form and a Jira field map, plus why each field matters and the mistakes that waste developer time.
What a QA engineer costs a US company in 2026: BLS salary figures, benefits on top, hiring time, hidden costs, and what drives the price of the alternatives.
A QA checklist for each startup stage, from first customer to growing team, and an honest comparison of hiring, outsourcing, managed QA and AI tools.
Risk-based testing for small teams: score each user flow for likelihood and impact, build a simple matrix, and let the score decide how deeply you test it.
A lean test plan template for small agile teams: what a formal test plan contains, a Markdown template to copy and a filled example for a web app.
One email is enough to start: your product, your platforms and how often you release. You get a plain answer on fit and, if it fits, a written proposal for the 60-day pilot with a short video of how we would test your product.
Or write to qa@releaseworthy.app. Still deciding after the proposal? We book a Google Meet call for your questions.