cabbage/rvbox
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: add production compose smoke harness

Browse Source
This commit is contained in:
cabbage
2026-09-11 06:28:11 +00:00
parent 110a329652
commit 248c41c7e1
9 changed files with 259 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/testing.md
+12
View File
@@ -193,6 +193,18 @@ Interactive browser access is a deliberately temporary recovery path only. See
self-signed HTTPS Guacamole lifecycle; it must be started only after the native
fixture controller has prepared and leased the VM, and stopped before reset.
The Linux production Compose asset has a separate, loopback-only smoke lane. It
uses a disposable self-signed key only under the ignored `.test-runs` tree,
starts the real non-root server and nginx services, probes TLS liveness and
readiness, and invokes `rvc` through the private socket. It leaves compact logs
and output for inspection, while removing its exact Compose project by default:
```sh
docker build -f deploy/Dockerfile.runtime -t rvbox-server:test .
scripts/test-production-compose run --run-id production-smoke
scripts/test-production-compose clean --run-id production-smoke --purge --yes
```
The canonical headless VirtualBox/Guest Control adapter is
`scripts/windows/test-host`. It is a POSIX controller script because the
fixture's VirtualBox host is Arch Linux and has no PowerShell runtime. The