test: prove native reconnect recovery
This commit is contained in:
+12
-5
@@ -70,8 +70,12 @@ default). Helium hosts the VM only; it does not host any RVBox server
|
||||
containers. The self-signed server certificate is intentionally accepted by
|
||||
the v1 client without a test CA. It then drives the installed SCM service
|
||||
through the server's real Unix control socket and verifies every Windows
|
||||
execution context. The tagged binary's controlled pre-launch failures are
|
||||
limited to the test fixture; a release binary rejects that switch.
|
||||
execution context, ordered stdin close, TERM delivery, and a server-process
|
||||
restart while a command is running. The restart check preserves the server
|
||||
state volume, waits for a new reconciled WSS session, then proves that the same
|
||||
command can receive its terminal signal; it covers reconnect without treating
|
||||
the old session as valid. The tagged binary's controlled pre-launch failures
|
||||
are limited to the test fixture; a release binary rejects that switch.
|
||||
|
||||
Successful runs collect bounded artifacts, remove only their labeled Compose
|
||||
project, and restore the exact clean snapshot. A failed or --keep run stays
|
||||
@@ -222,7 +226,7 @@ that mode-600 file; the controller never puts it on a command line, manifest,
|
||||
log, or artifact.
|
||||
|
||||
The native lifecycle is `status`, `prepare`, `stage`, `install`, `run`,
|
||||
`collect`, `stop`, and `reset`. `prepare` verifies the VM and snapshot UUIDs,
|
||||
`collect`, `logs`, `stop`, and `reset`. `prepare` verifies the VM and snapshot UUIDs,
|
||||
restores the clean baseline, starts headless, waits for Guest Additions, and
|
||||
proves that `RVBoxClient` is absent. `stage` copies a versioned non-secret test
|
||||
bundle through a run-specific host directory to a run-specific guest directory.
|
||||
@@ -230,8 +234,11 @@ bundle through a run-specific host directory to a run-specific guest directory.
|
||||
the real `rvbox.exe --install-service` path and proves completion through SCM.
|
||||
`run` is for reconfiguration/restart scenarios after that first installation.
|
||||
Neither action invokes the GUI-subsystem executable directly with the normal
|
||||
Guest Control account. `collect` obtains only bounded/redacted artifacts, and
|
||||
`reset` restores the exact clean baseline and leaves the VM powered off. It
|
||||
Guest Control account. `collect` obtains only bounded/redacted artifacts.
|
||||
`logs` is the narrow read-only service-startup/client-diagnostics action for a
|
||||
retained prepared run. The service diagnostic file grants access to SYSTEM and
|
||||
local Administrators only; it contains no command spool data. `reset` restores
|
||||
the exact clean baseline and leaves the VM powered off. It
|
||||
first permits a bounded ACPI shutdown; if that hangs, it force-powers off only
|
||||
the exact leased disposable VM before snapshot restoration. That intentional
|
||||
state loss is confined to the test isolation boundary.
|
||||
|
||||
Reference in New Issue
Block a user