docs: document smoke tests, integration tests, and add smoke-test command#811
docs: document smoke tests, integration tests, and add smoke-test command#811
Conversation
…mand - Add smoke testing and integration tests sections to CONTRIBUTING.md - Add smoke-test Cursor command for running tests against the live function - List smoke-test in the Cursor commands section Signed-off-by: Tomer Figenblat <tomer@figenblat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
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. 📝 WalkthroughWalkthroughA new Cursor IDE command configuration file is added for smoke testing, and the contributing guide is updated with documentation on smoke testing workflows, integration tests, required environment variables, and test fixture locations. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #811 +/- ##
=======================================
Coverage 99.20% 99.20%
=======================================
Files 8 8
Lines 1006 1006
=======================================
Hits 998 998
Misses 8 8 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@CONTRIBUTING.md`:
- Line 128: The long single line in CONTRIBUTING.md describing the Lambda
handler tests exceeds the 120-character limit; break that sentence into multiple
lines (wrap at sensible word boundaries) so each line is <=120 characters while
preserving the same text and links (retain references to
tests/app-runner.test.js, tests/fixtures/, and HMAC-SHA256/Probot/RSA key
wording), ensuring Markdown formatting remains unchanged.
- Around line 37-46: The CONTRIBUTING.md section describing the smoke test has
several lines exceeding the 120-character limit; wrap those long lines so no
line is longer than 120 chars (break at natural boundaries such as after
sentence ends, between list items, or within parentheses) while preserving
content and links for "node scripts/smoke-test.js ping", "node
scripts/smoke-test.js all", the ".github/workflows/smoke-test.yml" mention, and
the "tests/fixtures/" path; update the bullet list and paragraphs to use shorter
lines (or soft wraps) and ensure Markdown formatting and links remain intact.
Signed-off-by: Tomer Figenblat <tomer@figenblat.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
scripts/smoke-test.jstests/app-runner.test.jssmoke-testCursor command (.cursor/commands/smoke-test.mdc)Test plan
Summary by CodeRabbit