atago
Tests real CLI behavior from YAML specs checking exit codes, output, files and terminals.
Tested on macOS and Linux
Use it
macOS arm64
You need first
- Runtimes:
Go 1.26.10 or later
install atago via brew cask nao1215/tap/atago
brew install --cask nao1215/tap/atago
Check that it works
atago --versionThe output should contain “atago v0.25.2”.
First thing to try
cat > f1.atago.yaml <<'YAML'
version: "1"
suite:
name: example
scenarios:
- name: echo greets the world
steps:
- run:
shell: true
command: echo "hello atago"
- assert:
exit_code: 0
stdout:
contains: atago
stderr:
empty: true
YAML
cat > f2.atago.yaml <<'YAML'
version: "1"
suite:
name: files
scenarios:
- name: the generator writes the expected files
steps:
- run:
shell: true
command: mkdir -p site && echo "<html>hello</html>" > site/index.html
- assert:
file:
path: site/index.html
contains:
- "<html"
YAML
cat > f3.atago.yaml <<'YAML'
version: "1"
suite:
name: pty-test
scenarios:
- name: the init wizard completes
steps:
- pty:
command: sh -c 'printf "Project name: "; read name; echo "created $name/"'
session:
- expect: "Project name:"
- send: "demo\n"
- expect: "created demo/"
- assert:
exit_code: 0
YAML
cat > /tmp/prompt.sh <<'SH'
#!/bin/sh
printf "Project name: "
read name
echo "created $name/"
SH
chmod +x /tmp/prompt.sh
echo "setup done" && ls -lh *.atago.yaml
atago run f1.atago.yamlWrite a YAML spec file, then run it with atago run <spec>.atago.yaml.
Linux x86_64
You need first
- Runtimes:
Go 1.26.10 or later
Download prebuilt linux_amd64 tarball from releases and install atago to ~/.local/bin
mkdir -p ~/.local/bin /tmp/atago-dl && curl -fsSL -o /tmp/atago-dl/atago.tar.gz https://github.com/nao1215/atago/releases/download/v0.25.2/atago_0.25.2_linux_amd64.tar.gz && tar -xzf /tmp/atago-dl/atago.tar.gz -C /tmp/atago-dl && install -m 0755 /tmp/atago-dl/atago ~/.local/bin/atago && ~/.local/bin/atago --version
Check that it works
atago --versionThe output should contain “atago v0.25.2”.
First thing to try
mkdir -p specs && cat > specs/f1.atago.yaml <<'YAML'
version: "1"
suite:
name: example
scenarios:
- name: echo greets the world
steps:
- run:
shell: true
command: echo "hello atago"
- assert:
exit_code: 0
stdout:
contains: atago
stderr:
empty: true
YAML
cat > specs/f2.atago.yaml <<'YAML'
version: "1"
suite:
name: files-example
scenarios:
- name: the generator writes the expected files
steps:
- run:
shell: true
command: mkdir -p site && echo "<html>hello</html>" > site/index.html && cat site/index.html
- assert:
file:
path: site/index.html
contains:
- "<html"
YAML
cat > specs/f3.atago.yaml <<'YAML'
version: "1"
suite:
name: pty-example
scenarios:
- name: the init wizard completes
steps:
- pty:
command: sh -c 'printf "Project name: "; read name; echo "created $name/"'
session:
- expect: "Project name:"
- send: "demo\n"
- expect: "created demo/"
- assert:
exit_code: 0
YAML
ls -la specs/ && cat specs/f1.atago.yamlatago run specs/f1.atago.yamlWrite a YAML spec file, then run it with atago run <spec>.atago.yaml.
What it does
- Drive interactive prompts and terminal UIsTested
How to use it
- In a spec file, add a
ptystep with thecommandto run and asessionlist ofexpectandsendentries. - Add an
assertstep, for exampleexit_code: 0. - Run the spec with
atago run <spec>.atago.yaml.
- In a spec file, add a
- Record a real command run as a test specTested
How to use it
- Record a command with
atago record --out <spec>.atago.yaml -- <command>. - Replay the recorded spec with
atago run <spec>.atago.yaml.
- Record a command with
- Check a command's exit code, stdout and stderrNot shown working
- Check generated files and compare snapshotsNot shown working
How far pickfit got
macOS arm64
- Installs
- Starts
- 2 of 4 features work
- Works offline
Linux x86_64
- Installs
- Starts
- 1 of 4 features work
- Works offline
Other systems
Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- Check exit code, stdout and stderr of a command
- Check generated files and compare snapshots
- Drive interactive prompts and TUIs via PTY
- Record a real run into a test spec
- Test CLI against a background server
An alternative to runn, venom, ShellSpec and Bats.
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
macOS arm64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 1 Nov 2026
- Version v0.25.2
Differences the test machine hit
- README: brew install --cask nao1215/tap/atago
In the test: brew warns 'Calling `postflight` is deprecated! Use `postflight_steps` instead' but install still succeeds and binary is linked to /opt/homebrew/bin/atago
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version v0.25.2
Differences the test machine hit
- README: go install github.com/nao1215/atago@latest (requires Go 1.26.10+); yay -S atago-bin; aqua g -i nao1215/atago; mise use -g aqua:nao1215/atago
In the test: downloaded atago_0.25.2_linux_amd64.tar.gz from GitHub releases page (documented in README) and installed atago binary to ~/.local/bin - README: README wizard example uses a bare command without ': ' so needs no quoting
In the test: quote a pty/run command value containing ': ' in double quotes or it fails to load with ATG2003