🧪 Add success path test for post PATCH endpoint - #89
Conversation
Added a success case test for the PATCH method on the `/api/post/[id]` endpoint. The test fully mocks Supabase requests ensuring we expect a 200 response with the text 'Post updated' when all operations succeed. 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.
|
1 participant
🎯 What: Added a missing success-path test case for the
PATCHmethod in theapi/post/[id]endpoint. The existing tests only covered invalid input errors (400 responses).📊 Coverage: The new test covers a successful PATCH update operation, accurately mocking Supabase calls to
update,delete, andinsertstatements and verifying the correct 200 'Post updated' response.✨ Result: Increased test coverage for the post update API by verifying the success path, ensuring future modifications won't introduce regressions.
PR created automatically by Jules for task 11730217271857656632 started by @Sparkier