The zoecss-presets-tailwindcss4 preset should produce CSS output identical (or intentionally divergent) to actual Tailwind CSS v4 for the same input tokens. E2E tests would run both engines on a shared set of utility classes and diff the results, catching regressions and undocumented divergences.
Shares fixture needs with #12 (realistic inputs), but orthogonal: #12 focuses on performance benchmarks, this focuses on correctness verification. Not in scope: performance measurement (covered by #12), testing non-Tailwind presets.
Current state
Tests are unit-level per rule/module. No pipeline-level comparison against Tailwind CSS v4's actual output exists.
The
zoecss-presets-tailwindcss4preset should produce CSS output identical (or intentionally divergent) to actual Tailwind CSS v4 for the same input tokens. E2E tests would run both engines on a shared set of utility classes and diff the results, catching regressions and undocumented divergences.Shares fixture needs with #12 (realistic inputs), but orthogonal: #12 focuses on performance benchmarks, this focuses on correctness verification. Not in scope: performance measurement (covered by #12), testing non-Tailwind presets.
Current state
Tests are unit-level per rule/module. No pipeline-level comparison against Tailwind CSS v4's actual output exists.