Problem
The project currently has no automated tests. CI quality control is limited to lint, typecheck and a full build. There are no unit, integration or smoke tests, so changes to the build/release pipeline (icon generation, package exports, publishing) are not regression-protected.
This was surfaced during the review of #14 (React removal + publishing/Node changes), where there was no way to verify the build output still resolves after pipeline changes.
Suggested scope
- Pick a runner (e.g.
vitest) and add a test script.
- Build smoke test: after
pnpm run build, assert the Vue package entry imports cleanly and exports a non-empty set of components.
- Export integrity: verify generated
index.d.ts / per-style exports resolve.
- Metadata sanity: generated
metadata.json / info-metadata.json are valid and non-empty.
- Wire
pnpm test into the publish workflow before the publish steps.
Why
The publish pipeline can fail (or publish broken artifacts) silently — a minimal smoke layer would catch the most damaging regressions cheaply.
Filed as a follow-up to #14.
Problem
The project currently has no automated tests. CI quality control is limited to
lint,typecheckand a fullbuild. There are no unit, integration or smoke tests, so changes to the build/release pipeline (icon generation, package exports, publishing) are not regression-protected.This was surfaced during the review of #14 (React removal + publishing/Node changes), where there was no way to verify the build output still resolves after pipeline changes.
Suggested scope
vitest) and add atestscript.pnpm run build, assert the Vue package entry imports cleanly and exports a non-empty set of components.index.d.ts/ per-style exports resolve.metadata.json/info-metadata.jsonare valid and non-empty.pnpm testinto the publish workflow before the publish steps.Why
The publish pipeline can fail (or publish broken artifacts) silently — a minimal smoke layer would catch the most damaging regressions cheaply.
Filed as a follow-up to #14.