GoFish Graphics
Internals
Draft. This essay is a stub or a work in progress — read it as a sketch, not settled documentation.

Parity Testing ​

Because Python and JavaScript serialize to the same Frontend IR, a chart built in either language should render pixel-identically. Parity testing enforces that. This essay will document the workflow and its CI wiring.

Planned contents ​

  • How parity is captured and compared (JS DOM snapshots vs. Python-built charts).
  • The story/example format parity tests expect.
  • Common failure modes and how to triage them.
  • CI wiring: the js-capture job captures every JS story once and uploads it as an artifact. The python-parity job compares the Python capture against that JS capture, not against the snapshot baselines, so it runs in parallel with visual-test and a pending JS visual review does not hold it up.

Source ​

Likely covers:: the parity test harness under tests/ and packages/gofish-python/tests/. Add the covers: frontmatter when writing this up, then run pnpm --filter docs sync-backlinks.