Repository navigation
docs(agents): say which behavior deserves a test - #93
Conversation
Agents prove changes by using the app and add tests only where a regression would be costly or hard to notice: auth, RLS, billing, quotas, migrations, concurrency, parsers and fixed bugs. Lists the low-value tests not to write and keeps coverage thresholds Adam's call. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe PR adds guidance for selecting regression tests, including behaviors that warrant tests and tests to avoid. It also updates the testing documentation with a summary and a link to the guidance. ChangesTesting Guidance
Estimated code review effort: 2 (Simple) | ~8 minutes Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 2 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing. Comment |
Adds a What to test section to
AGENTS.md, plus a pointer fromdocs/testing.md.verify-debatelab. New tests are not a substitute.Docs-only.
npm run docs:checkpasses.🤖 Generated with Claude Code
Summary by CodeRabbit