Skip to main content

AEROSIM-TS-100

Project task

Verify the condition-selection round trip

Automated evidence proves that displayed, confirmed, launched, and runtime condition values are equal for every supported preset and representative custom combination.

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

Delivery scope

Create a table-driven condition integrity suite that covers every supported preset, minimum and maximum scalar boundaries, representative compatible custom combinations, rejected combinations, post-confirmation edits, launch failure, and a deliberate retry after correction.

Implementation contract

Implementation artifacts

  • applications/web/test/integration/condition-configuration-integrity.spec.ts
  • applications/web/test/fixtures/condition-configurations.ts

Inputs

  • The versioned condition catalogue and deterministic supported, boundary, and invalid fixtures.
  • Observed snapshots from the selector, launch configuration, and initialized session.

Outputs

  • A field-by-field integrity report for each fixture across draft, confirmation, launch, and runtime stages.
  • Test assertions proving a corrected retry creates one session without reusing failed launch state.

Failure boundaries

  • Any field mismatch, silent fallback, accepted invalid fixture, mutation of a confirmed snapshot, or session created by a failed attempt fails the suite.

Excluded scope

  • The suite does not establish performance or browser resource budgets.
  • The retry case is player-initiated after correction; background or repeated automatic retries are excluded.

Verification steps

  • Run applications/web/test/integration/condition-configuration-integrity.spec.ts with all condition fixtures.
  • Assert exact deep equality at each stage and assert each invalid fixture has its expected validation code.
  • Assert the failed-attempt session count is zero and the corrected deliberate retry increases it by exactly one.

Traceability

Requirements

Dependencies

UI/UX applicability

non_visual

This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.

Acceptance evidence

Verified delivery: application PR #130 merged reviewed head 827984b12a894c8fdeb0d8885e06467d5791021a as 432753c779413a604f873f06327f1ca2eb83afb9. The version-pinned table-driven integrity suite verifies all three supported presets, accepted scalar minima and maxima, a representative custom combination, exact displayed/confirmed/launch/runtime equality, explicit invalid-fixture codes, confirmed-snapshot immutability, zero sessions after a failed launch, and exactly one session after deliberate correction. Focused tests pass 15/15; web tests pass 1,081/1,081 plus invalid-action 11/11 and environment-presentation 27/27; lint, typecheck, formatting, production build, production audit, exact-head CI runs 4278-4279, and integration/publication runs 4280-4281 passed. 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.