puppetry
Puppetry is a no-code/low-code web test automation tool built on Puppeteer and Jest, designed to let non-developers create end-to-end browser tests through a UI. However, the project is officially deprecated as of the README, with the maintainer recommending Playwright as a superior alternative and noting that codeless testing has proven to be a technological dead end.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | dsheiko/puppetry |
| Owner | dsheiko |
| Primary language | JavaScript |
| License | MIT — OSI-approved |
| Stars | 892 |
| Forks | 127 |
| Open issues | 25 |
| Latest release | v3.2.6 (2021-08-16) |
| Last updated | 2026-06-19 |
| Source | https://github.com/dsheiko/puppetry |
What puppetry is
Puppetry wraps Puppeteer and Jest in an Electron desktop application, providing a GUI for recording browser flows, declaring element locators (CSS/XPath), managing BDD-style test structure, and exporting tests as Jest bundles for CI/CD. It supports visual regression, API testing, request mocking, and multiple browser engines (Chromium, Chrome, Firefox, Edge).
Get the puppetry source
Clone the repository and explore it locally.
git clone https://github.com/dsheiko/puppetry.gitcd puppetry# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Deprecated status: maintainer explicitly recommends Playwright as a superior alternative; evaluate long-term risk before adoption.
- Desktop Electron app required; no headless or server-side deployment model—tests run within the GUI or as exported Jest bundles.
- Export-to-Jest pathway mitigates some lock-in but requires manual re-integration if migrating away from Puppetry.
- Requires manual locator declaration (CSS/XPath); no built-in element inspection tools visible in docs.
- Limited to Puppeteer-supported browsers; Edge and Firefox support depends on Puppeteer backend stability.
When to avoid it — and what to weigh
- Starting New Project — Project is officially deprecated. Maintainer explicitly recommends Playwright for any new work, making Puppetry a risky choice for production adoption.
- Need Active Maintenance & Support — Latest release is v3.2.6 (August 2021). While repo shows recent activity (June 2026), deprecation status signals no feature development or bug fixes should be expected.
- Complex, Dynamic Test Scenarios — No-code UI limits expressiveness for sophisticated test logic, conditional flows, or advanced API interactions—tasks better suited to code-based frameworks.
- Team with Developer Resources — If your team can write code, Playwright, Cypress, or Selenium offer more control, better ecosystem support, and active development without the UI overhead.
License & commercial use
MIT License. Permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions (only requires license notice and disclaimer).
MIT license permits commercial use without restriction. However, deprecation status and lack of active maintenance mean commercial reliance on Puppetry is not recommended; license clarity does not offset lifecycle risk.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Stale |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Possible |
| Assessment confidence | High |
Puppetry runs as a local Electron app and generates Jest test bundles. Security posture depends on Puppeteer and Jest versions used; deprecated status means no ongoing security patching. Teams should audit exported Jest code before running in CI/CD. No explicit sandbox, secret management, or data handling guidance in available documentation.
Alternatives to consider
Playwright
Officially recommended by Puppetry maintainer; actively maintained, broader browser support, superior codeless + code-based flexibility, and thriving ecosystem.
Cypress
Modern, actively maintained, strong UI and debugging experience, excellent documentation, and better developer experience for E2E testing.
Selenium with cloud platforms (BrowserStack, Sauce Labs)
Industry standard with enterprise support, cross-browser coverage, CI/CD integration, and mature tooling if code-based testing is acceptable.
Build on puppetry with DEV.co software developers
Puppetry's maintainer has officially deprecated the project in favor of Playwright. If you're considering Puppetry for a new initiative, we recommend reviewing active alternatives (Playwright, Cypress, Selenium) that offer ongoing support and innovation. For legacy projects or educational use, Puppetry remains available but without active maintenance.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
puppetry FAQ
Is Puppetry still maintained?
Can I export tests for use in CI/CD?
What browsers does Puppetry support?
Do I need coding skills to use Puppetry?
Custom software development services
Need help beyond evaluating puppetry? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source devops integrations — and maintain them long-term.
Puppetry Is Deprecated—Evaluate Alternatives First
Puppetry's maintainer has officially deprecated the project in favor of Playwright. If you're considering Puppetry for a new initiative, we recommend reviewing active alternatives (Playwright, Cypress, Selenium) that offer ongoing support and innovation. For legacy projects or educational use, Puppetry remains available but without active maintenance.