test(api validation): check query validation boundaries for ?grace= parameter (Variation 1)

[souravjhahind]

🧩 Background

Input validation prevents arbitrary code and path traversal sequences from reaching the application core logic.

🎯 Objective

Write a schema-level validation test targeting the ?grace= parameter under positive range check.

📁 Files to touch

• app/api/streak/route.test.ts
• lib/validations.test.ts

🛠️ Implementation steps

• Mock a request passing the invalid value: -1.
• Assert that the validation handler returns a 400 Bad Request with 'grace must be an integer between 0 and 7'.

✅ Definition of done

• 1 new test case targeting the query input parameter.
• All endpoint test suites pass successfully.

[ThePriyanuj]

/claim

Hi @JhaSourav07,

I would like to claim this validation boundary testing task for the ?grace= query parameter! My local development environment is completely configured from my previous merged PR here, so I can roll out this implementation immediately.

🔬 My Planned Testing Implementation Strategy:

1. Schema Constraint Isolation: I will target lib/validations.test.ts to isolate the validation rule directly at the parser layer, ensuring that schema constraints successfully gate invalid ranges.
2. Boundary Negative Payload Test: I will modify app/api/streak/route.test.ts to mock an incoming API endpoint execution passing the negative parameter value -1 to explicitly trigger the lower bound error.
3. HTTP Status and Message Mapping: I will wrap the validation response pipeline inside an expected block assertion, verifying that it surfaces a strict 400 Bad Request payload coupled precisely with the error text: 'grace must be an integer between 0 and 7'.

I have the workspace pulled up locally and can submit a clean, isolated PR containing the new passing test cases right away. Thank you!

[github-actions]

❌ You already have 3/3 active assigned issues (the maximum allowed).
Please complete or /unclaim one of your current issues before claiming another.

📋 #1428 — test(api validation): check query validation boundaries for ?user= parameter (Variation 1)
📋 #1425 — test(mongodb): verify User schema behaviors under connection state 2 (connecting) (Variation 5)
📋 #1424 — test(mongodb): verify User schema behaviors under connection state 0 (disconnected) (Variation 5)