ci: run server/api and server/hocuspocus vitest suites in CI - #1019
Conversation
server/api's vitest suite (129 files / ~1,400 tests) was never run in CI — only api-typecheck (`bunx tsc --noEmit`) ran, so a broken suite could slip through unnoticed (e.g. the bun:test import in #992). server/hocuspocus had the same gap: its tests were only wired into the root `test:run` script, which CI does not execute (CI runs `test:coverage`). Add `api-test` and `hocuspocus-test` jobs mirroring the `mcp-test` setup (install deps inside the service dir, then `vitest run`), and align the misleading comment in the `test` job. Update AGENTS.md so the CI description matches reality, enumerating which job covers each service. Closes #1010
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
More reviews will be available in 5 minutes and 35 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the AGENTS.md documentation to accurately reflect the CI workflow jobs (api-test and hocuspocus-test) alongside the existing ones. It clarifies how each service (server/api, server/mcp, and server/hocuspocus) is individually installed and verified during CI. There are no review comments, so no feedback is provided.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
2 participants
server/api's vitest suite (129 files / ~1,400 tests) was never run in CI —
only api-typecheck (
bunx tsc --noEmit) ran, so a broken suite could slipthrough unnoticed (e.g. the bun:test import in #992). server/hocuspocus had
the same gap: its tests were only wired into the root
test:runscript,which CI does not execute (CI runs
test:coverage).Add
api-testandhocuspocus-testjobs mirroring themcp-testsetup(install deps inside the service dir, then
vitest run), and align themisleading comment in the
testjob. Update AGENTS.md so the CIdescription matches reality, enumerating which job covers each service.
Closes #1010