Skip to content

CI parity gate over committed EA reference SVGs - #216

Merged
HassanAkbar merged 1 commit into
mainfrom
lane/81-07-ci-parity-gate-over-committed-ea-referen
Nov 17, 2026
Merged

HassanAkbar merged 1 commit into
mainfrom
lane/81-07-ci-parity-gate-over-committed-ea-referen

Conversation

@HassanAkbar

Copy link
Copy Markdown
Member

CI parity gate over committed EA reference SVGs

Part of #54: EA parity: generated SVGs must be fully identical to EA's own SVG export (fonts, connectors, geometry)

Problem

Nothing in CI fails when output drifts from EA's export.

Fix

  • Add spec/ea/svg/parity/fixtures_gate_spec.rb: load the manifest model, run Suite against spec/fixtures/parity/refs, compare each diagram's delta counts with spec/fixtures/parity/baseline.yml, fail if any count increases, and report shrinkage so the baseline can be tightened
  • Generate the initial baseline.yml with the c6 task
  • Requires the EA-exported SVGs to be committed in spec/fixtures/parity/refs (maintainer-supplied)

Done when

  • the gate spec runs unskipped in bundle exec rake and passes against the baseline
  • a local edit that moves one element makes it fail

check.rb:
Warning! PATH is not properly set up, /Users/umerhassan/.rvm/gems/ruby-3.4.8/bin is not at first place.
Usually this is caused by shell initialization files. Search for PATH=... entries.
You can also re-add RVM to your profile by running: rvm get stable --auto-dotfiles
To fix it temporarily in this shell session run: rvm use ruby-3.4.8
To ignore this error add rvm_silence_path_mismatch_check_flag=1 to your ~/.rvmrc file.
specs: PASS 3 examples, 0 pending (1 files, 36s)
rubocop: PASS (1 files)

@HassanAkbar
HassanAkbar merged commit f0084eb into main Nov 17, 2026
29 of 31 checks passed
@HassanAkbar
HassanAkbar deleted the lane/81-07-ci-parity-gate-over-committed-ea-referen branch November 17, 2026 17:46
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.

1 participant