🧪 test: add database error path coverage for daily digest endpoint - #77
🧪 test: add database error path coverage for daily digest endpoint#77Sparkier wants to merge 2 commits into
Conversation
Co-authored-by: Sparkier <5690524+Sparkier@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: Sparkier <5690524+Sparkier@users.noreply.github.com>
🎯 What: The daily digest endpoint was missing coverage for the database error code path (e.g., when Supabase query fails with a 500 status).
📊 Coverage: A new test case was added to
server.test.tsto mock a Supabase return value with{ data: null, error: { message: 'DB Error' } }and verifies it throws anInternal Server Errorand correctly logs output.✨ Result: Test coverage for
src/routes/api/newsletter/daily-digest/+server.tsis more robust, effectively verifying error propagation from the DB client to the application response.PR created automatically by Jules for task 5332165038931161321 started by @Sparkier