feat(verify): add coverage enforcement to verify skill#3304
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Updates the /verify skill documentation to run Jest with coverage enforcement so verification fails when coverage drops below the thresholds configured in jest.config.js.
Changes:
- Switches infra-up test command from
npm run test:alltonpm run test:coverage. - Updates infra-down guidance to run unit-only tests with coverage and adds a note about threshold enforcement.
Summary
/verifyskill now runs tests with coverage enforcement (npm run test:coverage) instead of plainnpm run test:alljest.config.js(statements 80%, branches 65%, functions 80%, lines 80%), the verify step failsTest plan
/verifywith infra up — confirmsnpm run test:coverageexecutes and enforces thresholds/verifywith infra down — confirms unit-only coverage runs with warning