Custom-drawn controls
Buttons and grids painted straight to the screen look like controls to a person and like a blank rectangle to an accessibility API.
Custom-drawn grids and remote sessions break coordinate scripts. Qventis recognizes every control by sight and records each click as a plain-English step that runs the same every time.
Open the 'Ledger' app
Choose 'Journal' from the 'Entry type' list
Set cell 'Debit' to '{{entry.amount}}' on row 1
Click the 'Post' button
Check that the 'Balance' label shows '0.00'
Buttons and grids painted straight to the screen look like controls to a person and like a blank rectangle to an accessibility API.
Third-party and older components expose little to the tree, so scripts fall back to coordinates and break.
WinAppDriver is no longer actively maintained, per Microsoft's public repository. Teams built on it need a path forward.
The engine looks at the screen the way a tester does. It finds the 'Post' button by what it shows and where it sits.
Plain-English steps appear as you click. Each control gets one stored description that every test shares.
When an app arrives through a remote session, the test machine sees only pixels. Vision recognition works there too.
Start with one legacy app, then extend the same App Model to every channel.
No. Vision recognition works from what is on screen, so the app stays unchanged.
No. Recognition is compiled into the test ahead of time and runs deterministically.
Yes. Start with desktop alone and call the engine from your current framework through the CLI.
We record a flow with you and run it from the CLI.