Problem: No package.json in the repo defines a test script, despite a @cloner/test-utils package already existing. There is no coverage reporting and no CI test gate. This is currently the single biggest risk to shipping this as a paid product: a regression in the compiler output (packages/core) could silently break a customer's generated app with nothing catching it.
Proposed scope
Add unit tests for the compiler core (packages/core) covering the main transform paths (component extraction, token extraction, routing).
Add integration tests for the API endpoints (packages/api) using the existing @cloner/test-utils package.
Add a coverage threshold check to CI (ci.yml) that fails the build below a set percentage.
Document how to run tests locally in CONTRIBUTING.md.
Why it matters Without this, every release is a leap of faith for both maintainers and paying customers relying on deterministic output.
Problem: No package.json in the repo defines a test script, despite a @cloner/test-utils package already existing. There is no coverage reporting and no CI test gate. This is currently the single biggest risk to shipping this as a paid product: a regression in the compiler output (packages/core) could silently break a customer's generated app with nothing catching it.
Proposed scope
Add unit tests for the compiler core (packages/core) covering the main transform paths (component extraction, token extraction, routing).
Add integration tests for the API endpoints (packages/api) using the existing @cloner/test-utils package.
Add a coverage threshold check to CI (ci.yml) that fails the build below a set percentage.
Document how to run tests locally in CONTRIBUTING.md.
Why it matters Without this, every release is a leap of faith for both maintainers and paying customers relying on deterministic output.