How it works
À la carte, not a buffet.
Allwright isn't a separate tool for every surface wearing one brand — and it isn't one giant program trying to do everything either. It's a small core plus a plugin per surface: install the plugin for what you're testing, and the core knows how to drive it. Leave a plugin uninstalled, and the core simply doesn't attempt that surface yet.
One core, as many plugins as it needs
Every plugin is built from the ground up on allwright's own engine — not a wrapper around someone else's driver. Here's today's catalog; it grows as new surfaces ship.
$ allwright plugin list
$ allwright plugin install web
From your test code to the core
Bring your own language
Rust and Go clients are published and ready to install. Java, Python, and TypeScript clients are complete but not yet on a package registry — build them from source using the examples below.
Rust
PublishedThe engine itself, plus a high-level client.
View example →Go
PublishedA Playwright-style Browser and Page API.
View example →Java
From sourceA Gradle-based client for JVM test suites.
View example →Python
From sourceA client that feels at home in pytest.
View example →TypeScript
From sourceWorks from TypeScript or plain JavaScript.
View example →No drivers to babysit
Once you install the web plugin, allwright drives a real, current browser directly instead of going through a separate driver binary you have to download and version-match by hand. That means fewer “works on my machine” surprises, and tests that behave the way an actual person clicking through your app would.
Mobile, desktop, and API testing will work the same way once their plugins ship — no new tool to learn, just one more plugin install for whichever surface you need next.
Follow along as it ships
allwright is building in public. Star the repo to track progress, or head back home for the quick pitch.