Leapwork made its Play service available to teams managing Playwright test suites on September 30, 2026. As reported on November 17, 2026, the service adds requirements traceability and approval workflows around standard Playwright code. Teams can run that code in their existing continuous integration pipelines or use Leapwork’s hosted execution service.
Leapwork says teams can import existing Playwright suites without changes. Engineers can connect Jira, Git repositories and product documents to provide context for generated tests, or record browser interactions and turn them into test cases. According to the company, Play also watches connected repositories for pushes that may change an application’s behavior or interface, then recommends test updates.
For teams reviewing test changes, Play links each test to its originating requirement, ticket or document. Leapwork says it retains test-writing history, approvals and execution logs that teams can export as evidence. The service also reports flaky tests and test coverage across applications or teams. Role-based permissions and approval workflows control who can create and run tests, but the announcement does not specify which controls are included in the free plan. Leapwork says its enterprise plan includes the full governance, security and audit features.
Leapwork’s product page describes a “self-healing” feature that repairs failed test steps rather than failing a run outright. The available public information does not say whether teams can require human approval before locator repairs take effect or how those repairs appear in audit logs.
Play can also be used through AI coding assistants connected via a Model Context Protocol (MCP) server. Leapwork lists Claude Code, Codex and Cursor as clients and says its Chromium-based hosted service can run suites in parallel while managing environments and test data. Unlike Playwright’s open-source Trace Viewer, which helps diagnose individual runs through action details, network requests and screenshots, Play is positioned around managing test provenance and approvals across teams.


