Skip to main content

AEROSIM-TS-104

Project task

Verify control configuration integrity and invalid-control handling

Configuration-round-trip and invalid-control tests prove that only a successfully verified control profile reaches a session and that failures remain visible.

AEROSIM-TS-104Canonical ID TASK-0104
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — Input and launch integration test suites
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Create an integration matrix for each declared input method covering complete mappings, essential-action samples, device loss, malformed signals, profile edits after verification, token expiry and replay, controller initialization, and deliberate retry after reverification.

Implementation contract

Implementation artifacts

  • applications/web/test/integration/control-configuration-integrity.spec.ts
  • applications/web/test/fixtures/control-profiles.ts

Inputs

  • Declared control profiles, deterministic sample traces, and invalid token fixtures.
  • Observed mapping, diagnostic, launch, and SessionControlState records.

Outputs

  • A method-by-method integrity result proving the launched controller uses the verified profile.
  • Negative-case assertions for each invalid-control and token lifecycle code.

Failure boundaries

  • The suite fails on missing essential coverage, profile-hash mismatch, silent device substitution, reused token, duplicate session, or a failure without its expected code.

Excluded scope

  • Undeclared devices and custom remapping are not certified by this suite.
  • The suite does not claim end-to-end aircraft or world behavior.

Verification steps

  • Run applications/web/test/integration/control-configuration-integrity.spec.ts for the complete declared method matrix.
  • Assert mapping display, diagnostic profile, launch snapshot, and runtime controller share one profile hash.
  • Assert each failed attempt creates zero sessions and a reverification plus one deliberate retry creates exactly one.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: application PR #170 reviewed head 24041e97dbf0fc8ea5cd8c59fa22f4d66452c3d0 merged as f1d0180f54f36c8019209c6c24644c91922f925b. The 12-case behavioral matrix covers keyboard and joystick profile round trips; every declared diagnostic failure code; edited profiles; expired, substituted, and replayed tokens; device loss; controller initialization failure; zero-session failure behavior; and one deliberate retry after reverification. Exact-head CI run 4742 attempt 2 and feature run 4741 passed; integration run 4746 attempt 1 and immutable-image publication run 4745 attempt 2 passed. Harbor readback verified nebula sha256:a614a915c1231fdcfa0542dc2ec15c7be9cdbaa7850abe2eb41fd713df103ff3 and singularity sha256:66c78ec0aba8f3de7ecabd553f999ed9fc2b5c296887746fd445f0e38991a917. 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.