GUI testing that finds the control by what is on screen.
GUI testing in ZeuZ works on the screen the user sees: image recognition, OCR, coordinates and recorded events find and drive the controls that have no DOM and no accessibility tree, on web, Windows and macOS, in the same case as DOM-based steps. When the UI changes, the repair comes back as a diff, not a week of rewrites.
GUI testing checks an application through its graphical interface, the buttons, menus, fields, canvases and dialogs a user sees, rather than through its code or its APIs. ZeuZ automates GUI testing with 26 image-, OCR- and coordinate-based actions alongside its DOM-based web actions and UI Automation desktop actions, so a canvas, a map, a PDF viewer or a game screen is tested the same way as a form.
Where GUI testing breaks today.
The application draws its UI on a canvas, so there is no DOM, no ID and nothing for Selenium to click.
Coordinate scripts break on every screen size and every theme change, and nobody trusts the suite.
The visual check, is the right thing on screen, is done by a person with a screenshot folder.
How ZeuZ automates GUI testing.
- 01Test designProposes the screens a change touches from the tickets and the application's flows, ranked by importance.
- 02Test case creationDescribe what should be on screen and what to click in plain English; ZeuZ writes the case with the reference images and text it needs.
- 03Test automation26 GUI actions compile beside DOM and UI Automation steps: click and drag by image, click and read by OCR, hotkeys, coordinates, partial screenshots.
- 04Test executionRuns on your own Windows, macOS or web nodes, on a schedule or a CI webhook, with recorded .zvt events played back where needed.
- 05Reporting and analysisEvery step returns the screenshot with the matched region highlighted, so a miss is visible, not inferred.
- 06Test maintenanceWhen an icon or label changes, ZeuZ proposes the updated reference as a repair a person approves.
Your team reviews what ZeuZ produced. Nothing joins the suite or runs without a person accepting it.
See it run on your application.
Watch a UI change produce a proposed repair instead of a week of selector rewrites.
GUI test automation for screens with no DOM.
ZeuZ's GUI control actions use four ways to find a control: an uploaded reference image, OCR text with exact, partial or loose matching, X and Y coordinates, and playback of recorded .zvt event files. The 26 actions include check for element, click, double click and right click by image or by OCR, drag by images or to coordinates, hover, enter text, keystroke characters with delay, execute hotkey, find an item in a dropdown by scrolling, get a bounding box, get text by coordinates, by image or relative to other text, move the mouse, take a partial screenshot, wait for an element to appear or disappear, and launch a program by path.
They run on web, Windows and macOS, in the same case as DOM-based web steps and UI Automation desktop steps, so a test uses the DOM where there is one and the screen where there is not, which is what GUI testing needs on a canvas or a map. The AI Web Recorder, AI Windows Inspector and AI Mobile Inspector generate the DOM and tree locators; image and OCR cover the rest.
- Locate by
- Image, OCR (exact, partial, loose), coordinates, recorded events
- Actions
- 26: click, double, right, drag, hover, text, hotkeys, screenshot, wait, launch
- Text reading
- OCR by coordinates, by image, relative to text; bounding boxes
- Platforms
- Web, Windows, macOS
- Alongside
- DOM-based web actions, UI Automation desktop actions
- Tools
- AI Web Recorder, AI Windows Inspector, AI Mobile Inspector
Runs where your code is allowed to be.
Hosted by ZeuZ, execution on your own machines.
Point the client at your own server.
Disconnected environments, scoped per engagement.
Runs inside Jenkins, GitHub Actions, Azure DevOps, CircleCI and Bitbucket; results into Jira, Slack and Teams.
Works in the same suite as.
UI Automation trees for the desktop apps that do expose their controls.
Desktop application testing →The same screens checked across the browsers your users run.
Cross-browser testing →A WCAG 2.2 scan on the same rendered screens, kept as evidence per run.
Accessibility testing →Read next: Top 30 GUI testing tools →Related: Desktop application testing →
Ready to automate QA testing today?
See ZeuZ Test Studio write, run and repair tests against your own application code.
or explore our services →