What zriz tests and what it does not

zriz tests HTTP APIs, Postgres, and MySQL. On a deployed runner it also tests browser flows and command-line tools. It tests nothing else.

Question · zz 0.4.0 or later · Updated 2026-10-09 · Plain text for agents: /docs/supported.md

Which resource types does zriz have?

Four: http, sql, browser, and cli. There is no other type. Each run needs a runner.

With no runner, zz run gives the error runner-unavailable and the hint zz runners init --start. The runner guide tells how to get a runner.

Yes. A step calls an action of an http resource. A check reads the status and the body of the reply.

Yes. A step runs a query of an sql resource. A check reads rows and row-count.

The connection string has this form:

postgres://user:pass@host:5432/db

Yes. A step runs a query of an sql resource. A check reads rows and row-count.

The connection string has this form:

user:pass@tcp(host:3306)/db

No. zriz tests Postgres and MySQL. It tests no other database.

Yes. The runner needs the worker, a second container. zz runners init adds the worker to compose.yml when the project has a browser resource.

Yes. The runner needs the worker. The runner runs only the commands that its config permits.

zz runners init leaves a cli resource out of the config and names it in a warning.

macOS and Linux, on arm64 and x86_64. The install script stops on each other system. There is no install for Windows.

Yes. zz asks no question, and each command prints one JSON object. zz run ends with exit code 0 only when the status is pass.