DEV.co
Open-Source Testing · gemini-testing

testplane

Testplane is a TypeScript-based browser test runner built on Mocha and WebdriverIO, designed for end-to-end, integration, and component testing across multiple browsers and platforms. It provides visual testing, parallel execution, and a plugin ecosystem to support testing at scale.

Source: GitHub — github.com/gemini-testing/testplane
827
GitHub stars
74
Forks
TypeScript
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorygemini-testing/testplane
Ownergemini-testing
Primary languageTypeScript
LicenseMIT — OSI-approved
Stars827
Forks74
Open issues36
Latest releasev8.47.3 (2026-06-26)
Last updated2026-07-07
Sourcehttps://github.com/gemini-testing/testplane

What testplane is

Testplane (formerly Hermione) is a Node.js test automation framework offering WebDriver protocol support, visual regression testing with diff modes, cross-browser execution (Chrome, Firefox, WebKit), test sharding, isolated browser contexts, and a plugin-based architecture. It supports both Node.js and in-browser test execution for comprehensive coverage.

Quickstart

Get the testplane source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/gemini-testing/testplane.gitcd testplane# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Visual Regression Testing at Scale

Teams needing reliable screenshot-based assertions across multiple browsers and environments. Testplane's diff management UI and flakiness handling are suited for large test suites tracking UI changes.

Multi-Browser E2E & Integration Testing

Organizations testing against real device grids or diverse browser versions. Testplane's WebDriver abstraction and parallel execution enable efficient cross-platform validation without vendor lock-in.

Component Testing in Browser Environment

Teams running both e2e tests in Node.js and component/unit tests directly in browsers. Testplane's dual-environment support reduces toolchain fragmentation for full-stack test coverage.

Implementation considerations

  • Establish WebDriver endpoint(s) early—local Chromium, cloud grid (BrowserStack, Sauce Labs), or self-hosted Selenium. Configuration scope is broad; document target environment matrix upfront.
  • Plan visual baseline management: baseline images must be version-controlled and synchronized across environments. Diff acceptance workflow requires process discipline to prevent false positives.
  • Plugin ecosystem extensibility is available but requires custom development for many common tasks (reporting, CI integration). Audit plugin maturity before depending on community plugins.
  • TypeScript support is native but config and plugins may have looser typing. Validate type safety requirements; fallback to JavaScript is possible.
  • Test flakiness handling (retries, auto-wait) is built-in; configure thresholds and timeouts per suite to avoid masking genuine failures.

When to avoid it — and what to weigh

  • Need Native Mobile Testing Out-of-the-Box — Testplane requires WebDriver-compatible grids for mobile; native iOS/Android automation is not built-in and requires third-party service integration.
  • Enterprise SLA/Support Requirements — Testplane is community-maintained open-source with no commercial support tier mentioned. Organizations requiring guaranteed response times or dedicated vendor support should evaluate commercial alternatives.
  • Minimal DevOps/Configuration Tolerance — Testplane requires manual setup of browser grids, configuration files, and plugin management. Teams preferring zero-config, fully managed solutions may find setup overhead significant.
  • Heavy Reliance on IDE Plugins or Ecosystem — Testplane ecosystem tooling (IDE integration, CI/CD templates) maturity is not documented. Adoption relative to Cypress or Playwright may mean fewer third-party integrations available.

License & commercial use

MIT License. Permissive open-source license allowing commercial use, modification, and distribution with minimal restrictions. Attribution recommended; no warranty provided.

MIT license explicitly permits commercial use, modification, and redistribution. No vendor lock-in or commercial license upsell observed. However, no commercial support channel, indemnification, or SLA is documented; commercial users assume full operational responsibility.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

No security audit, penetration test results, or vulnerability disclosure program documented. As a test runner executing automation code, consider: (1) test code injection risks if test files are user-supplied, (2) credentials in config or environment variable exposure, (3) WebDriver endpoint security (local vs. cloud grid). Isolate test execution environments and use secrets management best practices.

Alternatives to consider

Cypress

Modern, developer-friendly, strong IDE support and zero-config defaults. Trade-off: less cross-browser support (Chrome-based rendering), no native visual regression, smaller enterprise adoption in traditional QA.

Playwright

Multi-browser (Chromium, Firefox, WebKit), fast, good DevX, strong Microsoft backing and ecosystem. Trade-off: visual regression not built-in, steeper learning curve for non-WebDriver users, less plugin extensibility.

WebdriverIO

WebDriver-native, multi-browser, plugin ecosystem. Trade-off: lower-level abstraction, more configuration required, smaller visual testing story, community-driven (no vendor backing).

Software development agency

Build on testplane with DEV.co software developers

Schedule a technical review with our team to assess fit for your browser testing strategy, WebDriver infrastructure, and CI/CD pipeline. We'll help you scope implementation complexity and identify required customization.

Talk to DEV.co

Related 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.

testplane FAQ

How does Testplane differ from Playwright or Cypress?
Testplane emphasizes visual regression testing, WebDriver protocol flexibility, and a mature plugin architecture. Cypress is simpler but Chrome-centric. Playwright is fast and multi-browser but lacks built-in visual diffing and has weaker plugin extensibility.
Can I run tests locally and on a cloud grid with the same codebase?
Yes. Testplane configuration supports multiple browser endpoints. Switch between local (e.g., localhost:4444) and cloud grids (BrowserStack, Sauce Labs) by config change; tests remain unchanged.
Is Testplane suitable for CI/CD?
Yes, but setup is manual. Testplane CLI supports headless execution, JUnit/JSON reporting, and exit codes. You must author CI/CD pipeline scripts; no native GitHub Actions or Jenkins plugins are documented.
How is visual baseline management handled?
Baseline images are stored as PNG files in a version-controlled directory. Diffs are compared on each run; acceptance workflow is CLI-driven or GUI-based. Git or equivalent VCS is required to track baseline changes.

Work with a software development agency

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If testplane is part of your open-source testing roadmap, our team can implement, customize, migrate, and maintain it.

Ready to Evaluate Testplane for Your Test Automation?

Schedule a technical review with our team to assess fit for your browser testing strategy, WebDriver infrastructure, and CI/CD pipeline. We'll help you scope implementation complexity and identify required customization.