68 lines
3.7 KiB
Markdown
68 lines
3.7 KiB
Markdown
# Verification scope
|
|
|
|
Regression commands:
|
|
|
|
```sh
|
|
go test -race -count=1 ./...
|
|
go vet ./...
|
|
python3 -m unittest discover -s scripts -p 'test_*.py'
|
|
```
|
|
|
|
Optional no-inference stable OpenCode checks:
|
|
|
|
```sh
|
|
PIPELINES_TEST_OPENCODE_V1=/path/to/opencode \
|
|
go test ./internal/opencode ./internal/author -run TestStable -count=1 -v
|
|
```
|
|
|
|
The stable checks use isolated home/config/data/cache directories; they never
|
|
copy login credentials or invoke a model. They exercise session creation, explicit
|
|
model selection, stored scoped permissions, abort on the same owned service,
|
|
session deletion, and discovery of the installed global authoring skill. Authoring
|
|
now references that skill directly instead of preloading instructions.
|
|
|
|
Native generation/assistant completion parsing is regression-tested against a
|
|
controlled HTTP server. Full live inference, permission enforcement by real model
|
|
tool calls, cancellation during inference, optional Docker deployment, privileged
|
|
system-wide copying, and OS service-manager registration are **not tested**.
|
|
|
|
Autostart regression tests exercise both service-definition formats, scoped
|
|
environment capture, escaping, private files, refusal to overwrite unmanaged
|
|
files/symlinks, preview without side effects, and lifecycle calls using a mock OS
|
|
manager. The installed macOS CLI's preview was validated with `plutil -lint`.
|
|
`GOOS=linux GOARCH=amd64 go build ./cmd/...` also passed. Actual launchd/systemd
|
|
registration, logout/login restart, and Linux lingering remain **not tested**.
|
|
|
|
An isolated installed-CLI check started the server in one directory and invoked
|
|
`pipelines run` from two other directories. With a mock OpenCode executable, both
|
|
runs completed and recorded/executed in the client invocation directory. The
|
|
autostart preview required no repository configuration and passed `plutil -lint`.
|
|
CLI and dashboard regression tests also check invocation-directory selection.
|
|
|
|
The installation tests were also executed as a Linux binary in Debian with
|
|
systemd installed. The native `systemd-analyze verify` regression passed for the
|
|
generated unit, including a directory containing spaces, quotes, and `%`/`$`.
|
|
This reproduced and fixed the invalid quoted `WorkingDirectory` setting. A
|
|
container syntax check does not prove live user-service startup or login restart.
|
|
|
|
Authoring regression tests exercise idempotent skill installation, preservation of
|
|
user modifications, one direct OpenCode launch with a short skill/context reference,
|
|
and an unnamed new draft without CLI questions. TUI integration checks browse a
|
|
CLI-style retained draft, validate through the server, require explicit submission
|
|
confirmation, preserve create-only guards, and reject a different server.
|
|
|
|
An isolated installed-binary PTY check also opened a CLI-created draft in the TUI,
|
|
reopened the same file through a mock OpenCode executable, and explicitly submitted
|
|
it while retaining the draft. Plain unnamed CLI creation invoked the mock exactly
|
|
once. Real model-driven authoring/questions and native skill loading during a
|
|
model turn remain **not tested**; global skill discovery was tested without inference.
|
|
|
|
An installed-binary integration check executed a Bash/QML fixture through a mock
|
|
OpenCode backend: it changed README/QML, created a new text file, and actually ran
|
|
`bash -n install.sh`. Both JSON and PTY supplied-task runs started without approval
|
|
flags, file lists, or typed confirmation, in the invocation directory rather than
|
|
the server directory. Permission regression tests cover language-neutral shell,
|
|
project file types/new files, optional narrower scopes, and outside-edit denials.
|
|
Real model/tool-permission enforcement remains **not tested**. Shell uses the host
|
|
user's authority; these policies are not an OS sandbox.
|