Eve library

Bellona Deployment Smoke Test Plan

Guide

Revision 1

On this page

Status: 180.C.16.08 deterministic fixture coverage.

Implementation date: 2026-04-23.

This plan adds automated smoke coverage for local, same-LAN, Hetzner reference, and AWS reference deployment modes. It validates that each mode has a concrete gateway profile, protocol network mode, probe list, smoke commands, evidence requirements, and reusable fake gateway-host command path. It does not claim live cloud, physical MacBook, TLS, firewall, TURN, Blender, Unreal, browser, or desktop deployment evidence yet.

Sources Reviewed#

Local implementation references:

  • testing/bellona/remote-control/fake-gateway-transport.ts
  • testing/bellona/remote-control/fake-host-adapter.ts
  • testing/bellona/remote-control/network-impairment.ts
  • testing/bellona/remote-control/security-regression.ts
  • testing/bellona/remote-control/performance-budgets.ts
  • docs/domains/bellona/extras/remote-control/local-cloud-agent-simulation.md
  • docs/domains/bellona/extras/remote-control/blender-read-only-mvp-second-macbook.md
  • docs/domains/bellona/extras/remote-control/mvp-alpha-operations-runbooks.md
  • docs/domains/bellona/extras/remote-control/hetzner-reference-deployment.md
  • docs/domains/bellona/extras/remote-control/aws-reference-deployment.md
  • docs/domains/bellona/extras/remote-control/hardware-rig-inventory.md
  • libs/bellona/mcp-gateway/src/cloud-agent-mvp-smoke.ts
  • libs/bellona/mcp-gateway/src/remote-mac-no-inbound-smoke.ts
  • apps/bellona/remote-host/scripts/*remote-smoke.ts

Automated Modes#

testing/bellona/remote-control/deployment-smoke.ts exposes createRemoteControlDeploymentSmokePlan(), runRemoteControlDeploymentSmokeScenario(), and runRemoteControlDeploymentSmokeSuite().

The deterministic suite covers:

Mode Gateway profile Network mode Fixture coverage Live evidence still required
local ephemeral-loopback offline-fixture In-process gateway/host path, device list, command dispatch, readiness, audit Local app startup and packaging evidence remain separate
lan same-lan-outbound-host same-lan Same-LAN metadata, outbound-only host path, routed diagnostic readiness, audit Two-MacBook run with gateway URL, host identity, routed smoke, and audit export
hetzner hetzner-reference-edge cloud-gateway Reference contract for TLS health/readiness, private app port, WSS route, logs Hetzner region/server id, DNS, firewall, service logs, bind proof, commit SHA
aws aws-reference-edge cloud-gateway Reference contract for ALB/TLS readiness, private service boundary, target check AWS account/region, VPC, ALB target health, security groups, logs, commit SHA

Every scenario result now reports both liveDeploymentEvidenceRequired and releaseSignoffEligible. LAN, Hetzner, and AWS fixture success must keep releaseSignoffEligible=false until the live evidence listed above is attached; the local deterministic fixture is the only signoff-eligible result for the local contract itself.

Smoke Commands Tracked#

The suite records the commands that operators or release jobs must run in each mode as the deployment surfaces become available:

  • local: pnpm nx cloud-agent:mvp-smoke @bellona/mcp-gateway, pnpm nx remote-mac:no-inbound-smoke @bellona/mcp-gateway, pnpm nx blender:scene-info-remote-smoke @bellona/remote-host, pnpm nx browser:managed-remote-smoke @bellona/remote-host
  • LAN: pnpm nx remote-mac:no-inbound-smoke @bellona/mcp-gateway, pnpm nx blender:scene-info-remote-smoke @bellona/remote-host, pnpm nx blender:create-primitive-remote-smoke @bellona/remote-host, pnpm nx desktop:fallback-remote-smoke @bellona/remote-host
  • Hetzner: public HTTPS /health and /ready, recent gateway and Caddy logs, and local 4070 bind proof from the server
  • AWS: public HTTPS /health and /ready, ALB target health, recent gateway logs, and security-group evidence that 4070 is not public

Release Gate Rules#

The alpha gate can use this suite to verify that every deployment mode has a stable smoke contract and a protocol-valid diagnostic command path. The suite must not be used as a substitute for live evidence in modes marked live-hardware-required.

Before MVP alpha can claim deployment readiness, release evidence must attach:

  • local smoke output for the cloud-agent and no-inbound host paths
  • two-MacBook LAN smoke output, topology, host identity, and audit export
  • Hetzner public TLS readiness, firewall/bind proof, service logs, and commit SHA
  • AWS public TLS readiness, ALB target health, security groups, service logs, and commit SHA
  • explicit notes when TURN, WebRTC media, live Blender, live Unreal, browser, or desktop workflows are still outside a deployment trial

Verification#

The committed automated gate is:

bash
pnpm exec vitest run --config vitest.config.ts tests/deployment-smoke.test.ts --reporter=verbose
pnpm nx run-many -p @bellona/remote-control-testing -t lint,typecheck,test,build --skip-nx-cache --verbose

The first command proves the individual deployment modes and canonical suite order. The second command keeps the reusable test harness buildable and covered by Nx.