Puppetry is a no-code/low-code end-to-end web testing tool built on top of Puppeteer and Jest, aimed at QA engineers, testers, and developers who want to record and manage browser tests through a UI instead of writing scripts — though the project is now officially deprecated and kept only as an example and a piece of its own history.

What it is

Puppetry is a test automation tool for end-to-end testing of web applications that wraps Puppeteer headless Chrome and the Jest test runner behind a graphical interface. Instead of authoring selector logic and assertions by hand, users pick browser methods and assertions from a predefined list with predefined settings and extensive inline tips, then compose those steps into runnable browser tests. The project is written in JavaScript and distributed under the MIT licence, with 888 stars, 127 forks, and 25 open issues on GitHub.

The concrete problem it solves is the gap between teams that need E2E coverage and the engineering effort required to write and maintain that coverage. Puppetry replaces hand-written Puppeteer scripts with a recorder and a BDD-style editor: a user records a user flow, declares element targets as pairs in the form variable = locator where the locator is either a CSS selector or an XPath expression, and organises the resulting work in a hierarchy of project, suite, test context, and test case. The recorded project can then be exported as a Jest/Puppeteer bundle that a continuous integration server runs in a CLI, so the codeless authoring step feeds a standard code-based pipeline rather than replacing it.

Key capabilities

• Built-in automation recorder captures a user flow and turns it into editable test steps.
• Element targets declared as variable = locator pairs, with locators written as CSS selectors or XPath expressions.
• BDD-style test organisation across project, suite, test context, and test case levels.
• Test execution against Chromium, Chrome, Firefox, and Edge browsers.
• Export as a Jest/Puppeteer project bundle, ready to plug into a CI/CD pipeline.
• Export as a human-readable test specification that includes screenshots captured per test step.
• Staging, template variables, and expressions for configurable and reusable test scenarios, plus reusable snippets.
• Git version control integration and Allure test report support.

Who uses it and how

• QA engineers with no programming background can author and maintain E2E suites through the UI, which is the primary audience the README names.
• Development and testing teams export the project as a Jest/Puppeteer bundle and run it from a CI server rather than inside the editor.
• Teams covering distinct testing types the documentation calls out, including functional testing, testing of dynamic content, and visual regression work.
• Testers validating responsive web design, covered by a dedicated walkthrough in the project's video material.
• Users who prefer step-by-step navigation of a running test, through an interactive mode described as similar to Cypress.

Getting started

The README points to the hosted site at https://puppetry.app and to the project documentation, and tagged builds are published through GitHub Releases, with v3.2.6 as the latest download. The documentation covers export for CI at docs.puppetry.app, and getting-started guidance lives under the same docs domain.

How it compares

Puppetry is layered on two tools that are not its competitors but its foundation: Puppeteer supplies the headless Chrome control and Jest supplies the runner, and the export format is exactly that pairing. Its main overlap is with Playwright, which the deprecation notice states has evolved to cover almost everything Puppetry originally aimed to achieve, and does so better. Cypress is referenced only as the reference point for Puppetry's interactive step navigation, which is a single feature rather than a replacement claim.

When to use it — and when not to

Do not start new work on Puppetry. The maintainer, Dmitry Sheiko, has officially deprecated it, calling codeless end-to-end testing a technological dead end and pointing to Playwright for the capabilities it once targeted. Anyone who needs browser end-to-end coverage today should adopt Playwright, or generate tests through AI-assisted development by narrating the intended outcome, rather than operate a UI editor whose upstream direction has been abandoned. The repository remains useful as a reference implementation of a recorder-driven Puppeteer and Jest workflow and as an example of the codeless-testing approach, and the README gives no indication of resumed maintenance.

sudo snap install puppetry

brew cask install puppetry