test: weekly coverage improvement 2026-06-14#79
Conversation
- Extended streaks.test.js with formatDateInTimezone, getHourInTimezone, getActivityHeatmap tests - New comments.test.js: 14 tests covering getComments, getBatchCommentCounts, postComment, deleteComment - New nudges.test.js: 5 tests covering sendNudge with auth, rate limiting, and error paths - New cronAuth.test.js: 6 tests covering verifyCronSecret with timing-safe comparisons - New email.test.js: 6 tests covering sendReminderEmail with mocked Resend, including XSS escaping - Added limit to supabase-mock.js chain methods - All tests pass with coverage improvements (statements 79.86% → 89.38%) Co-Authored-By: Claude Scheduled Task <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
toLocaleString with hour12:false returns 24 for midnight on some Node/ICU versions. Accept both 0 and 24 as valid.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 421106f039
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ]); | ||
|
|
||
| const result = await postComment(supabase, 'a1', longText); | ||
| expect(result.success).toBe(true); |
There was a problem hiding this comment.
When notification truncation regresses and postComment sends the complete 100-character comment, this test still passes because it only checks the function's success result. Inspect the notification builder.insert call and assert that its message contains exactly 60 characters plus the ellipsis so the behavior named by the test is protected.
Useful? React with 👍 / 👎.
| ]); | ||
|
|
||
| const result = await sendNudge(supabase, 'target-user'); | ||
| expect(result.success).toBe(true); |
There was a problem hiding this comment.
When the sender profile is absent, removing the 'Someone' fallback would produce an undefined nudged you... notification while this test remains green because sendNudge still returns success. Assert the notification insert's message so this test actually protects the fallback behavior in its title.
Useful? React with 👍 / 👎.
- comments: verify truncated message is exactly 60 chars + ellipsis - nudges: verify "Someone" fallback appears in notification message
2 participants
Weekly Test Coverage
Automated PR from the scheduled coverage task.
What changed
docs/reports/coverage-2026-06-14.mdNew test files
tests/unit/lib/comments.test.jsgetComments,getBatchCommentCounts,postComment,deleteCommenttests/unit/lib/nudges.test.jssendNudge(auth, rate limiting, happy path, errors)tests/unit/lib/cronAuth.test.jsverifyCronSecret(timing-safe token comparison)tests/unit/lib/email.test.jssendReminderEmail(mocked Resend, XSS escaping)Extended tests
tests/unit/lib/streaks.test.jsformatDateInTimezone,getHourInTimezone,getActivityHeatmapFiles going from 0% to covered
comments.js: 0% → 100%nudges.js: 0% → 100%cronAuth.js: 0% → 100%email.js: 0% → 95.23%streaks.js: 49% → 91.5%Mock helper update
limittosupabase-mock.jschain methods (unblocksnudges.jstesting)Scope
Tests follow the existing Vitest + happy-dom conventions in
tests/unit/lib/. React components, context providers, and animation presets are out of scope.Test results
All 233 tests pass.
Generated by Claude Code