Revyl adds CLI‑to‑natural‑language tests
- Revyl rolled out a CLI workflow for mobile app testing that lets developers define and run end-to-end checks in natural language from the terminal. - The concrete hook is where it runs: Revyl says those YAML-backed tests execute on cloud iOS and Android devices and slot into CI. - It matters because mobile teams still fight flaky selector-heavy tests, and Revyl is betting agent-friendly CLI tooling lowers that maintenance tax.
Mobile testing is one of those jobs everybody agrees matters and almost nobody enjoys maintaining. The pain is familiar — selectors break, UI shifts, and the test suite turns into a second app you have to babysit. Revyl’s new push is to make that feel less like writing brittle automation and more like telling a system what a user should do. The change is centered on its CLI, which now leans hard into natural-language test creation and execution for mobile CI workflows. ### What did Revyl actually add? The short version is a terminal-first way to create, edit, sync, and run tests defined in YAML, but described in plain language rather than hand-authored selector logic. Revyl’s docs frame the CLI as the full control surface for the platform — not just a helper tool — and explicitly pitch it as something you can hand to coding agents like Cursor, Claude Code, or Codex. ### What does “natural language tests” mean here? It does not look like Revyl is claiming magic free-form reasoning on every run. The product surface it shows is natural-language steps like “Book a ride to SFO” or “Tap ‘Buy’ and confirm order,” with those steps stored in files and synced with a visual editor. Basically, the human writes intent, and Revyl handles the device interaction layer underneath lower scripts, less hand-maintained glue code. ### Why put this in the CLI? Because the CLI is where this becomes usable in real engineering workflows instead of just a demo in a dashboard. Revyl’s quick-start flow runs through `revyl init`, `revyl build upload`, and `revyl test run`, and the company keeps emphasizing local-first, git-friendly automation. That matters because teams want tests to live next to the code, show up in pull requests, and run automatically before merge. ### Why is mobile the interesting target? Mobile is where brittle automation hurts the most. Native apps, React Native,
