A WinAppDriver alternative — Windows desktop testing that is still maintained

Microsoft's WinAppDriver — the WebDriver implementation for Windows desktop apps — has been archived, and teams who built their Windows UI tests on it are looking for a way forward. Playwright and Cypress will not help: they are web-only by design. Here is how TITA Automation compares, and what a move actually involves.

What WinAppDriver got right

WinAppDriver did something no web tool does: it drove native Windows applications — WinForms, WPF, UWP and Win32 — through the same WebDriver protocol teams already knew from Selenium. You wrote tests in your own language, ran them in your own CI, and reused Selenium skills on the desktop. That combination is why it ended up in so many pipelines.

The gap it leaves

No maintenance. An archived driver does not follow Windows, the applications it automates, or the accessibility stack underneath it. What works today is the high-water mark.
Web tools do not cover it. Playwright, Cypress and Selenium automate browsers. A workflow that touches a desktop app and a web app needs two tools and a seam between them.
Selectors break and nothing heals them. Automation ids change between builds, and every break is a person reading a stack trace and editing a locator by hand.
Everything is code. Fine for engineers who enjoy it, a wall for the testers who know the application best.

How TITA Automation fits

Windows desktop automation, actively developed. It drives native Windows applications through the accessibility tree — automation id, name, class and control type — with image matching as a fallback when a control exposes nothing useful.
Desktop and web in one test. One workflow can open a desktop app, read a value, then check it in a browser — no seam, one run, one report.
Record instead of write. Point at the application and work through it; the steps are captured as you go, and you can still edit every selector by hand.
Selectors that heal themselves. When a control moves or is renamed, AI healing relocates it and the run carries on, instead of failing overnight and waiting for a person.
Your CI still gates on the result. Trigger a run from Jenkins, GitHub Actions, Gitea or Azure Pipelines over a simple API and fetch JUnit XML back, so the pipeline you already have keeps working the way it does.
Runs on your own machines. Desktop tests need a real Windows session; agents run on your hardware and report to a cloud portal with screenshots and step timelines.

Capability	WinAppDriver	TITA Automation
Windows desktop automation	✓	✓
Actively maintained	archived	✓
Web automation in the same test	—	✓
Record-based authoring	—	✓
Self-healing selectors	—	✓
Screenshots, step logs, reporting	build it yourself	✓
CI triggers + JUnit output	via your own code	✓
Requires writing code	always	optional
Cost	free (unmaintained)	free · Pro $29/mo

What moving actually involves

There is no importer, and we would rather say so than pretend. WinAppDriver tests are code; TITA tests are recorded steps with selectors you can edit. In practice teams re-record their critical paths — usually faster than porting the code — and keep the automation ids they already have, because TITA locates controls the same way, through the Windows accessibility tree. Your CI integration stays: trigger a run, poll it, read JUnit.

When to choose which

Stay on WinAppDriver if your suite is stable, your engineers are comfortable maintaining it, and you accept that it will not be updated again.

Choose TITA if you want Windows desktop testing that is still developed, web tests in the same workflow, recording instead of hand-written locators, and healing when selectors drift — with your pipeline still deciding whether the build passes.

Try it on the app you are testing now

Record a Windows desktop test in minutes — free plan, no card required.

Start free — no card