Available now
Web
Chromium and Firefox with semantic locators, iframes, uploads, downloads, state reads, and retrying assertions — ready for real test suites.
v0.1.28 – v0.1.34 — ready to try today
One automation engine for everything you test.
Web, mobile, desktop, and API — allwright is one small core engine with an installable plugin for each surface. It's à la carte, not a buffet: your team learns one system, and installs only the plugin for what it's actually testing.
Built from the ground up — no wrapped drivers, no glued-together tools.
À la carte, not a buffet
The core stays small. Every surface below is an optional plugin.
Available now
Mobile
Android and iOS Simulators or registered devices run natively with automatic runtime and app setup, exposing the same Playwright-style client shape.
macOS + Windows available
Desktop
Native macOS and Windows application automation through installable plugins, with no Appium or WinAppDriver; Linux is next.
Not yet available
API
Backend checks written in the same test, alongside the same browser flow.
“Available now” means installable today and ready to use in your test suite. See the detailed breakdown →
New: Allwright Inspector
Point at an element. Get the locator.
allwright inspector shows your running Android, iOS, macOS, or Windows app next to its accessibility tree, then writes the locator for you in TypeScript, Python, Java, Go, or Rust.
Why allwright
À la carte, not a buffet
The core stays small on its own. Each surface is a plugin you install on purpose, so you never carry the weight of automation you don't use.
Built from the ground up
No wrapped drivers, no glued-together tools. Every plugin runs on allwright's own engine, engineered to behave the way a real user does — so results stay dependable, not flaky.
One workflow, every team
Web, mobile, desktop, and API testers describe automation the same way, so knowledge and coverage carry across the whole product as each plugin ships.
Write your first test in a minute
One command scaffolds a config, a starter test, and dependencies. Or see how the plugin model fits together first.