Skip to main content

AEROSIM-TS-107

Project task

Verify the initial-camera configuration round trip

Automated evidence proves equality between the displayed, confirmed, launched, and initially active camera for every supported option.

AEROSIM-TS-107Canonical ID TASK-0107
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — Pre-flight and camera integration test suites
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Create a table-driven camera integrity suite for every supported option, registry changes, unsupported identifiers, post-confirmation edits, construction failure, first-frame activation, and a deliberate retry after selecting a valid camera.

Implementation contract

Implementation artifacts

  • applications/web/test/integration/initial-camera-integrity.spec.ts
  • applications/web/test/fixtures/camera-options.ts

Inputs

  • Supported and invalid camera fixtures plus observed selector, launch, and first-frame state.

Outputs

  • Per-camera equality assertions across displayed, confirmed, launched, and initially active identifiers.
  • Retry assertions proving a failed camera attempt leaves no session or frame.

Failure boundaries

  • Any identifier or registryVersion mismatch, fallback substitution, frame emitted before activation, or session retained after failure fails the suite.

Excluded scope

  • Camera transitions after the initial frame and camera visual quality are not evaluated.
  • Only a new deliberate launch after correction is tested; automatic retries are excluded.

Verification steps

  • Run applications/web/test/integration/initial-camera-integrity.spec.ts for all camera fixtures.
  • Assert exact cameraId and registryVersion equality at all four stages and firstFrameSequence equals zero.
  • Fail one launch, correct the camera, retry deliberately, and assert one and only one session and initial frame are created.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: application PR #172 reviewed head 1c3f6a80acbb999b1628349cc39b66377ed5ffee merged as b1b4e3caf98ec4094608a90e1ab2e4fadda3d6f7. The table-driven initial-camera suite covers all four supported cameras and exact cameraId/registryVersion equality from displayed option through immutable confirmation, launch configuration, and initially active camera at firstFrameSequence 0. Unsupported identifiers, registry-version drift, removed cameras, post-confirmation selection edits, construction failure, fallback prevention, and deliberate corrected retry all fail closed or retain exactly one successful session and frame. The focused suite passes 12/12 and adjacent camera suites pass 70/70; the full web suite passes 1336/1336 plus browser flight and Playwright E2E suites. Lint, typecheck, formatting, security, container contract, production build, and production dependency audit pass. Candidate CI run 4765 attempt 1, integration validation run 4767 attempt 1, and immutable image publication run 4766 attempt 1 passed. Harbor readback resolved Nebula digest sha256:71f2af1e08f9e3a855fcb874aeffcf7c5932dca4d47b6ef6ba6f41a732aa49e0 and Singularity digest sha256:10eae457219bcb4b7008a3afc83d9bb5d4d4769ce5536a21a19f7d08178af1af for the exact integration revision. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.