🧪 Add test for Formspree fetch failure in contact API#69
🧪 Add test for Formspree fetch failure in contact API#69
Conversation
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@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.
|
🎯 What: Added missing test coverage for the Formspree fetch failure path in
app/api/contact/route.ts.📊 Coverage: Now tests the scenario where Formspree returns a non-OK status (simulated using mocked
global.fetchreturningok: false). It verifies the endpoint logs the error correctly viaconsole.errorand responds with a 500 status code and appropriate error message.✨ Result: Improved test coverage and reliability of the contact API by ensuring the failure handler behaves exactly as expected. Also introduced a native
node:testsetup withtsxadded as a dev dependency and a"test"script.PR created automatically by Jules for task 14048666322974483495 started by @hatimhtm