Skip to main content

AEROSIM-TS-110

Project task

Verify complete pre-flight configuration integrity

End-to-end evidence proves that each reviewed configuration creates one session whose world, aircraft, conditions, controls, and initial camera exactly equal the summary.

AEROSIM-TS-110Canonical ID TASK-0110
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Web Application — End-to-end pre-flight and flight integration test suite
Repository
corp-v1-aerosim/corp-v1-aerosim

Delivery scope

Create an end-to-end integrity suite that selects representative aircraft, world, condition, control, and camera combinations; confirms one source revision; renders its summary; issues launch; and compares every runtime snapshot with the same configurationHash while exercising stale summaries, invalid controls, concurrent duplicates, and retry boundaries.

Implementation contract

Implementation artifacts

  • applications/web/test/e2e/preflight-launch-integrity.spec.ts
  • applications/web/test/fixtures/preflight-configurations.ts

Inputs

  • Representative valid and invalid complete pre-flight fixtures and injectable launch-stage failures.
  • Observed summary, launch result, runtime configuration, and session count.

Outputs

  • A field-level integrity result for all five configuration sections and the shared hash.
  • Duplicate and retry evidence recording clientLaunchId, sessionId, terminal result, and session count.

Failure boundaries

  • Any field mismatch, accepted stale summary, accepted invalid control token, reused launch identifier creating another session, partial session, or unclassified launch failure fails the suite.

Excluded scope

  • The suite ends when the launched runtime configuration is established; it does not score the flight, produce a debrief, update progress, write session history, or start training content.
  • Performance targets belong to their specific quality tasks and are not inferred from functional integrity.

Verification steps

  • Run applications/web/test/e2e/preflight-launch-integrity.spec.ts for all complete fixtures.
  • Assert deep equality for aircraft, world, conditions, controls, and camera plus equality of sourceRevision and configurationHash.
  • Exercise stale-summary, invalid-token, concurrent duplicate, pre-commit failure, post-commit response loss, and corrected deliberate retry cases; assert the expected terminal result and exact session count.

Traceability

Requirements

Dependencies

Acceptance evidence

Verified delivery: application PR #179 reviewed head 8275ab007b1c480d1f45f9cfb7caac41ae4405ff merged as c6fce1621188762754a244b7907e5b786c2bf7e8. Eight focused integrity tests across two representative complete fixtures prove field-level aircraft, world, conditions, controls, and initial-camera equality; shared sourceRevision and configurationHash; stale-summary and invalid-control rejection; concurrent and replayed duplicate identity; classified pre-commit failure with deliberate corrected retry; post-commit response-loss recovery; and exact session counts. Full repository-native validation, container, Helm, production audit, candidate CI run 4869 attempt 2, integration CI run 4875 attempt 1, and immutable publication run 4874 attempt 2 passed. Harbor readback resolved Nebula digest sha256:99e491abffa74a63d5d43aedd88747e3c93ca45fc3d03afabc66902b10ee354e and Singularity digest sha256:459c4cb36f3c81e17ba15fa63fcd31c1ab1ee2d6a6039d01d0afd363d748fd19 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.