Demo Site: add unit testing setup with Vitest

[VPS-Obi]

Adds a unit testing setup to the site. This was first proposed in vivid-planet/dextinity-starter#395 and rejected due to no real world examples. However, since some of our projects already have a unit testing setup in the site (e.g., an online shop) and writing unit tests becomes effortless with agentic coding, I suggest to revise this decision and add a unit testing setup to the Demo/Starter.

https://claude.ai/code/session_01BTrAyuuTjXFqBTp9ip9bXp

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 886ee293-b95d-43b7-8571-ab035b4d46f4

📥 Commits

Reviewing files that changed from the base of the PR and between 504c97f and fd992cd.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• .github/workflows/test.yml
• demo/site/package.json
• demo/site/src/util/createSitePath.test.ts
• demo/site/vitest.config.ts

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The demo site now uses Vitest for unit tests. Its configuration enables jsdom, TypeScript path resolution, and JUnit output. New createSitePath tests cover valid and invalid paths. CI uploads the generated JUnit reports.

Changes

Vitest unit-test reporting

Layer / File(s)	Summary
Vitest setup and unit coverage demo/site/package.json, demo/site/vitest.config.ts, demo/site/src/util/createSitePath.test.ts	The demo site adds Vitest scripts and development dependencies. The configuration enables jsdom, TypeScript path resolution, excluded directories, default and JUnit reporters, and JUnit output. Tests cover language prefixes and invalid paths.
JUnit artifact upload .github/workflows/test.yml	The unit-test artifact upload now includes demo/*/junit-unit.xml reports.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to fd992

This PR adds a localized Vitest unit-testing setup and CI test command without any supplied evidence of merge-blocking correctness, security, availability, or deployment risk; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: adding a Vitest unit testing setup to the demo site.
Description check	✅ Passed	The description explains the addition of unit testing to the demo site and provides relevant context for the change.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/vitest-unit-test-setup-rb8b8v

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved at fd992cd

Macroscope's review found this PR approvable — This PR adds isolated Vitest tooling, a focused unit test, lockfile entries, and CI report collection without changing production application code or customer request behavior. Its runtime impact is confined to local and CI test execution.

^{You can add or adjust custom eligibility rules. Learn more.}