Files
yushanhe f097f5bc21
designops-gateway / build (push) Failing after 20m0s
chore: bootstrap DesignOps monorepo (5 subprojects + OKF + annotations)
- merge openpencil/penpot/excalidraw/style-dictionary/storybook as native
  monorepo code (upstream .git removed; origins in okf/manifest.md)
- add project-level okf/ (manifest + memory/rule/skill/decision/lesson)
- add AGENTS.md (OKF annotation standard) + monorepo .gitignore
- annotate 9 entry files with @module/@skill/@rule headers
- add GitOps deploy bundle (infra/gitops/) + Gitea CI (.gitea/workflows/)
2026-09-27 21:28:44 +08:00
..

Style Dictionary Integration Tests

Style Dictionary is a tool to generate valid source code for multiple platforms and languages to consume. Because of this, unit testing can only get us so far. Simply unit testing or even basic snapshot testing of outputs doesn't give the whole picture.

The integration tests here are meant to show complete end-to-end examples of Style Dictionary being used in order to validate the files it is generating.

The integration tests still use Jest and snapshots, but rather than singling out format code, each test group builds a complete Style Dictionary and then tests the content of the output files with snapshots and validating syntax where possible.

To do

  • Jest snapshots are a good built-in way to test if content has changed, but storing the contents of a source code file like a CSS variables file doesn't get proper syntax highlighting and validation in IDEs. It would be better if we could store the raw output file and test against the new contents, but snapshot testing does not allow for that.
  • Add more syntax validations