Skip to content

test: the CSV export pins carry the sentences the application writes today - #56

Merged
Paullo9 merged 2 commits into
mainfrom
issue-42-pin-constants
Oct 31, 2026
Merged

Paullo9 merged 2 commits into
mainfrom
issue-42-pin-constants

Conversation

@Paullo9

@Paullo9 Paullo9 commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Requested by Paul · project thread

Fixes #42

Summary

Tests/ImagoFFTTests/Fixtures/csv-export-pins.json pinned the radial-profile and spots CSV sentences as macTEM wrote them when the pins were made, with internal milestone ids in the validation and lineage lines. macTEM main has since dropped those ids: its FFTExport sentences now say "ImagoKit's parity tests" and "carries no lineage id". The fixture now carries those current sentences.

  • The three constants are replaced with macTEM main's current sentences.
  • Each expected file text gets the same sentences substituted verbatim (22 files, 44 lines). No input and no other byte of any expected text changes.
  • New test pinnedSentencesNameNoMilestone: it fails on the old fixture and passes on the new one.

The fixture move is its own commit, with the reason.

Test evidence

  • Red first: pinnedSentencesNameNoMilestone failed with 4 issues on the old fixture.
  • swift test -c release --parallel --skip ImagoKitParityTests: all green, including the byte-for-byte radial and spots writers against the moved pins.

🤖 Generated with Claude Code

…today

csv-export-pins.json held the radial-profile and spots validation sentences and
the lineage sentence as the application wrote them when the pins were made, with
internal milestone ids in them. The application has since dropped those ids and
now names what each number is checked against (ImagoKit parity tests) and says
the FFT room carries no lineage id, without promising one for later.

The fixture moves for that reason only: the three constants are replaced with
the current sentences, and each expected file text has the same sentences
substituted verbatim (22 files, 44 lines). No input and no other byte of any
expected text changes. The kit writers reproduce every pinned file byte for byte,
as before. A new test, pinnedSentencesNameNoMilestone, fails on the old fixture
and passes on the new one.

Done: the CSV export pins name no internal milestone. Next: none for this issue.

Fixes #42

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Paullo9 Paullo9 self-assigned this Oct 31, 2026
@Paullo9
Paullo9 merged commit d5563a5 into main Oct 31, 2026
6 checks passed
@Paullo9
Paullo9 deleted the issue-42-pin-constants branch October 31, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

csv-export-pins.json constants name internal milestone ids

1 participant