Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Playwright for Rust
🎭 Rust language bindings for Microsoft Playwright
Status: 🚧 Active Development - Not yet ready for production use
🎯 Why playwright-rust?
Read our WHY.md to understand the vision, timing, and philosophy behind this project.
TL;DR: Rust is emerging as a serious web development language, with frameworks like Axum and Actix gaining traction. AI coding assistants are making Rust accessible to more developers. Test-Driven Development is experiencing a renaissance as the optimal way to work with AI agents. These trends are converging now, and they need production-quality E2E testing. playwright-rust fills that gap by bringing Playwright's industry-leading browser automation to the Rust ecosystem.
Roadmap and Goals
See Development Roadmap for plans and status of the development approach for playwright-rust.
Goal: Build this library to a production-quality state for broad adoption as @playwright/rust or playwright-rs. Provide official-quality Rust bindings for Microsoft Playwright, following the same architecture as playwright-python, playwright-java, and playwright-dotnet.
How It Works
playwright-rust follows Microsoft's proven architecture for language bindings:
┌──────────────────────────────────────────────┐
│ playwright-rs (Rust API) │
│ - High-level, idiomatic Rust API │
│ - Async/await with tokio │
│ - Type-safe bindings │
└─────────────────────┬────────────────────────┘
│ JSON-RPC over stdio
┌─────────────────────▼────────────────────────┐
│ Playwright Server (Node.js/TypeScript) │
│ - Browser automation logic │
│ - Cross-browser protocol abstraction │
│ - Maintained by Microsoft Playwright team │
└─────────────────────┬────────────────────────┘
│ Native protocols
┌─────────────┼─────────────┐
▼ ▼ ▼
Chromium Firefox WebKit
This means:
- ✅ Full feature parity with Playwright (JS/Python/Java/.NET)
- ✅ Cross-browser support (Chromium, Firefox, WebKit)
- ✅ Automatic updates when Playwright server updates
- ✅ Minimal maintenance - protocols handled by Microsoft's server
- ✅ Production-tested architecture used by millions
API Design Philosophy
Following Playwright's cross-language consistency:
- Match Playwright API exactly - Same method names, same semantics
- Idiomatic Rust - Use Result, async/await, builder patterns where appropriate
- Type safety - Leverage Rust's type system for compile-time safety
- Auto-waiting - Built-in smart waits like other Playwright implementations
- Testing-first - Designed for reliable end-to-end testing
Installation
Add to your Cargo.toml:
[]
= "0.8" # Auto-updates to latest 0.8.x
= { = "1", = ["full"] }
See the CHANGELOG for version history and features.
Browser Installation (Required)
Important: Browsers must be installed separately using the Playwright CLI.
The library bundles Playwright driver version 1.56.1. You must install matching browser versions:
# Install all browsers (recommended)
# Or install specific browsers
Why version matters: Each Playwright release expects specific browser builds. Using playwright@1.56.1 ensures you get compatible browsers (chromium-1194, firefox-1495, webkit-2215).
In CI/CD: Add this to your GitHub Actions workflow:
- name: Install Playwright Browsers
run: npx playwright@1.56.1 install chromium firefox webkit --with-deps
The version constant is also available in code:
use PLAYWRIGHT_VERSION;
println!;
What happens if I don't install browsers? You'll get a helpful error message with the correct install command when trying to launch a browser.
Development
Prerequisites
- Rust 1.85+
- Node.js 18+ (for Playwright server and browser installation)
- tokio async runtime
Building from Source
# Clone repository
# Install pre-commit hooks
# Build
Installing Browsers
After building, install browsers as described in Browser Installation above:
The build script automatically downloads the Playwright driver to drivers/ (gitignored). CI handles browser installation automatically - see .github/workflows/test.yml.
Platform Support: ✅ Windows, macOS, Linux
Running Tests
Note: This project uses cargo-nextest for faster test execution. Install it once globally:
# All tests (recommended - faster)
# All tests (standard cargo)
# Integration tests only (requires browsers)
# Specific test
# With logging
RUST_LOG=debug
# Doc-tests (nextest doesn't run these)
# See CLAUDE.md "Documentation Testing Strategy" for details
# Compile-only check (fast, used in pre-commit)
# Execute all ignored doctests (requires browsers, what CI does)
# Execute specific crate's doctests
Running Examples
Note: See examples/ for usage examples.
# Run a single example
# Run all examples
for; do
||
done
Contributing
This project aims for production-quality Rust bindings matching Playwright's standards. Contributions should:
- Follow Playwright API conventions
- Include comprehensive tests
- Maintain type safety
- Document public APIs with examples
- Pass CI checks (fmt, clippy, tests)
License
Apache-2.0 (same as Microsoft Playwright)
Acknowledgments
- Microsoft Playwright Team - For the amazing browser automation framework
- playwright-python - API design reference
- Folio Project - Initial driver for development needs