Skip to content

🧪 test: add missing-field error path test for contact API#66

Open
hatimhtm wants to merge 1 commit intomainfrom
test/contact-api-missing-field-11080214693524475361
Open

🧪 test: add missing-field error path test for contact API#66
hatimhtm wants to merge 1 commit intomainfrom
test/contact-api-missing-field-11080214693524475361

Conversation

@hatimhtm
Copy link
Copy Markdown
Owner

🎯 What: The testing gap addressed
The contact API (app/api/contact/route.ts) was missing test coverage for the initial validation branch, which throws a 400 error when one or more of the required fields (name, email, brief) are missing from the request body.

📊 Coverage: What scenarios are now tested
The app/api/contact/route.test.ts now explicitly covers:

  • Missing email
  • Missing name
  • Missing brief
  • All fields missing

Result: The improvement in test coverage
Increased the coverage of error edge-cases for form submissions, ensuring the frontend won't encounter unexpected server 500 exceptions if data shape rules are violated. Also updated the NPM test script configuration to run tests with tsx properly resolving extensions.


PR created automatically by Jules for task 11080214693524475361 started by @hatimhtm

Added a test for the contact API route covering the scenario where required fields are missing in the request body. Tested using node test runner using custom require hook to bypass Next.js server module resolution limitations.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
portfolio Ready Ready Preview, Comment Mar 21, 2026 11:21am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant