Leapwork Play Reaches GA with Governance for Playwright Tests

Leapwork made Play generally available on September 30, 2026 for teams managing Playwright test suites. The service adds requirement traceability and approval workflows around standard Playwright code, which teams can run in their existing continuous integration (CI) pipelines or through Leapwork's hosted execution service.

In its announcement, Leapwork says Play imports existing Playwright suites without changes. Engineers can connect Jira and Git repositories, along with product documentation, to build a knowledge base that supplies context for generated tests. They can also record a browser journey and turn the recording into a test.

Leapwork says Play monitors connected repositories for pushes that change application behaviour or the interface, then recommends corresponding test updates. Separately, its product page describes self-healing that fixes broken test steps instead of failing a run. The sources do not explain whether teams can require approval before a locator repair is accepted or how such repairs are recorded in the audit history.

For teams that need to review test changes, Play links each test to its originating requirement, ticket or document. Leapwork says the service retains authoring history and approvals alongside full execution logs, which teams can export as evidence. The service also reports flaky tests and coverage across applications or teams.

Role-based permissions and approval workflows control who can create and run tests. Leapwork includes the full governance, security and audit capabilities in enterprise packages, but the announcement does not specify which individual controls are available in the free tier.

Donovan Brady, vice-president of developer relations at Leapwork, described the management problem in the announcement: "What slows an enterprise team down now is proving where a test came from and managing thousands of them across dozens of teams once they exist."

Teams can also operate Play through an AI coding assistant using a server for the Model Context Protocol (MCP). Leapwork's product page names Claude Code, Codex and Cursor as clients and describes its hosted execution as Chromium-based. Leapwork says its hosted service runs suites in parallel, including environment and test data management.

Open-source Playwright already provides failure diagnostics through its Trace Viewer, including action details, network requests and screenshots. Those facilities help engineers investigate individual runs; Play's additional scope is central management of test provenance and approvals across teams.