Testing & QA
Leapwork Play Adds Test Governance Layer to Playwright Automation
A new platform brings requirement traceability and approval workflows to Playwright test suites, targeting teams managing test sprawl at scale.
InfoQ
Leapwork launched Play as a general-availability product in September 2026, offering governance and traceability features designed for teams running Playwright test suites. The service wraps standard Playwright code with approval workflows, requirement links, and audit trails while integrating with existing CI pipelines or Leapwork's own hosted execution infrastructure.
How It Works#
Play integrates directly with existing Playwright test suites without requiring rewrites. Teams can connect Jira, Git repositories, and product documentation to establish context for test generation. The platform also supports browser journey recording—users can capture workflows and convert them into automated tests.
The service monitors Git pushes for changes that might affect application behavior or UI, then suggests test updates in response. A self-healing feature automatically repairs broken test locators rather than failing runs, though the platform does not currently clarify whether teams can gate these repairs behind approval gates or audit them in detail.
Centralized Test Management#
Rather than scattering test ownership across multiple repositories, Play creates a unified view of test provenance, authoring history, and execution logs. Each test maps back to its source requirement, ticket, or documentation. Teams can export this chain of evidence for compliance, review authoring and approval records, and track which tests are flaky or have incomplete coverage across applications and teams.
Access controls rely on role-based permissions and approval workflows, restricting who can create and modify tests. Leapwork offers full governance and audit features in enterprise packages, though the announcement does not detail which controls appear in the free tier.
AI Integration and Execution#
Users can manage tests through an AI coding assistant connected via the Model Context Protocol (MCP), with support for Claude Code, Codex, and Cursor. Leapwork's hosted service runs test suites in parallel using Chromium and handles environment and test data provisioning automatically.
Context and Competition#
Open-source Playwright already ships with the Trace Viewer, which provides failure diagnostics including action logs, network activity, and screenshots for individual test runs. Play's differentiation lies in centralizing test provenance, approvals, and coverage metrics across distributed engineering teams.

