Repository navigation
refactor(tests): align test files with unit testing rubric - #84
Conversation
- ai-tools.test.ts: Add @scaffold label, replace brittle key counting with spread-equality assertion, add collision detection test - page-write-tools.test.ts: Remove weak "only called" assertion, rely on observable outcomes (result.success, result.linesReplaced) - mcp-bridge.test.ts: Remove call count assertion, keep payload assertions - drive-tools.test.ts: Remove unused chain mocks, add @scaffold note with TODO for DriveRepository seam - search-tools.test.ts: Remove unused chain mocks, add @scaffold note with TODO for SearchService seam These changes follow the unit testing rubric principles: - Test observable outcomes, not internal mechanics - Mock only at boundary seams - Label scaffold/aggregation tests appropriately - Document deferred happy path coverage with seam proposals
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded@2witstudios has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 59 seconds before requesting another review. ⌛ 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. 📒 Files selected for processing (5)
✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai help |
ChatThere are 3 ways to chat with CodeRabbit:
CodeRabbit commands
Other keywords and placeholders
CodeRabbit configuration file (
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai resume |
✅ Actions performedReviews resumed. |
These changes follow the unit testing rubric principles: