Formulon

English

日本語

English

日本語

Appearance

CI Regression Workflows ​

Formulon is useful in CI when spreadsheet outputs are part of your product contract. Formula or calculated-value changes become explicit diffs that PR reviewers can classify.

Glossary: parity runner

A repo-internal test runner that evaluates shared fixtures across every available channel (WASM, Native Node, Python, CLI) and reports both missing channels (binding not built) and mismatched results (channels disagree on a value). Run with make parity-test.

Snapshot formulas ​

sh
formulon dump --formulas model.xlsx > model.formulas.txt
git diff --exit-code model.formulas.txt

This catches formula edits without depending on cached calculated values. The dump is cheap — no recalculation — so it can run on every PR.

Snapshot recalculated values ​

sh
formulon recalc model.xlsx -o /tmp/model.recalc.xlsx --quiet
formulon dump --values /tmp/model.recalc.xlsx > model.values.txt
git diff --exit-code model.values.txt

Use this for golden-output tests. dump --values recalculates first, then prints every non-blank cell in stable sheet/cell order. Pair it with the formula snapshot when both authoring drift and value drift matter.

Compare package surfaces ​

The repository includes a parity runner:

sh
make parity-test

It evaluates shared fixtures across available channels and reports missing channels separately from mismatched results. Use it when changing bindings or packaging.

Parity vs oracle

The parity runner checks that our own surfaces agree with each other. The oracle testing flow checks that we agree with Excel. Both are useful: parity is a fast pre-commit signal, oracle is the compatibility ground truth.

When not to use CI snapshots ​

Avoid direct snapshots for formulas that include volatile functions such as NOW, TODAY, RAND, and RANDBETWEEN unless the fixture controls or documents the volatility. The same applies to functions that depend on external services (web / cube), which can produce different values on different CI runners.

For volatile-heavy workbooks, snapshot the formulas only (dump --formulas) and verify representative cells through a script that asserts ranges or shapes rather than exact values.