unotest documentation

Your agent writes the E2E tests. You review and commit. Plain .js in your repo, a local viewer, full human control.

Start building

Quick start — web npx @unotest/web init → ask your agent → run → review.

Quick start — iOS Point it at a built .app and ask your agent for a test.

How it works MCP, semantic snapshots, a sandboxed engine, local-first.

Install & setup Node, browsers, and wiring your editor over MCP.

Scenarios & step()

Tests are readable on top, precise underneath. Every step is step("intent", () => { … }) — plain-English intent over real DSL calls. Read more

The Viewer

A local IDE for your tests: live runs, a step debugger, collections, variables — no cloud, no account. Tour the viewer

Reference

Auto-generated from the code: CLI, DSL, config, MCP tools.

For your AI agent

MCP-native. Connect Claude Code / Cursor / Codex and let the agent drive. Docs are machine-readable too: llms.txt.