aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md12
1 files changed, 11 insertions, 1 deletions
diff --git a/README.md b/README.md
index cbbbec6..41ad3f6 100644
--- a/README.md
+++ b/README.md
@@ -145,6 +145,7 @@ dingger does not need tmux running first; it attaches when a server appears.
```bash
cargo test # engine tests + herdr state-machine tests
tests/e2e.sh # end to end against an isolated tmux server
+tests/pi-live.sh <pi> # a real pi binary against dingger (new pi releases)
```
`tests/e2e.sh` starts its own tmux server, its own daemon (polling only every
@@ -157,6 +158,15 @@ ranking, selection), the status-line segment, latency with a
deliberately slow notifier, and state surviving a daemon restart. It never
touches your tmux server.
+`tests/pi-live.sh <pi binary>` checks a real pi release on a tmux server and
+daemon of its own, with a fake local model (`tests/fake-model.py`) and its
+own pi agent directory: no network, no credentials, your pi untouched. It
+covers identification, the extension's state and session reports, a turn,
+`/reload`, an extension's blocked event, screen detection without the
+extension, restore, and exit. To try a release without installing it:
+`npm install --prefix /tmp/pi-next @earendil-works/pi-coding-agent@<version>`
+(through `sfw`), then `tests/pi-live.sh /tmp/pi-next/node_modules/.bin/pi`.
+
## Layout
- `crates/detect-core`: the detection engine and 22 manifests, from herdr.
@@ -164,4 +174,4 @@ touches your tmux server.
- `menubar/`: the menu bar app (`model.swift` rows and colors, `panel.swift`
the floating panel, `hotkey.swift` the global shortcut and settings).
- `packaging/`: launchd agents and the tmux snippet.
-- `tests/e2e.sh`: the end-to-end suite.
+- `tests/e2e.sh`: the end-to-end suite; `tests/pi-live.sh`: a real pi.