Kery automates web app QA by crawling apps and filing bugs
Kery is an autonomous QA tool for web apps. A developer points it at a URL, runs `npx keryai`, and it crawls routes, forms, and modals to map what is actually in the app. Tests are written in plain English, such as checking whether checkout finishes successfully, and Kery decides how to carry them out.
It is built to avoid the upkeep that often comes with Playwright scripts, , and XPath. Instead of relying on brittle page-code locations, it uses the and screenshots to understand what buttons, fields, and screens mean. That should make tests less likely to fail just because a developer moved or renamed something.
In a nightly staging workflow, Kery reports broken flows, visual problems, and user-experience issues in a dashboard with screenshots and marked problem areas. A triage agent uses memory from earlier runs to reduce duplicate and .
Key points
- Kery crawls web app routes, forms, and modals from a URL.
- Tests can be described in plain English instead of hand-written scripts.
- It avoids heavy reliance on and XPath, which often break after UI changes.
- Nightly staging runs can surface broken flows, visual regressions, and usability issues.
- A triage agent reduces repeated reports and using memory from past runs.