You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Missing Negative Test Coverage for Backend APIs #65
Most backend tests currently check only the successful (happy-path) cases.
In real usage, external services like GitHub API, Gemini AI, and FAISS can fail, timeout, or return unexpected data.
These failure scenarios are currently not covered by tests.
Steps to Reproduce
Call backend APIs with an invalid or expired GitHub token
Simulate an empty or malformed response from GitHub or Gemini
Trigger a network timeout or service failure
Observe that failures are not properly handled or tested
Expected Behavior
The backend should:
Handle failures gracefully
Return clear and safe error responses
Have test cases that validate this behavior
Actual Behavior
Failure scenarios are not tested, which may lead to:
Silent crashes
Unclear error responses
Bugs appearing only in production
Component
Backend
Environment
Backend (FastAPI, AI services, FAISS)
Backend service (environment-independent)
Additional Context
This issue focuses only on adding test coverage.
No API behavior or features will be changed.
I’d like to work on this issue as part of SWoC — please assign it to me if approved.
Hey @SrishtiSonam , Valid issue - accepted! This is important for production reliability, but please prioritize after rate limiting (#66) is implemented.
Activity
github-actions commentedon Jan 3, 2026
Thank you for creating this issue! 🎉
This issue is part of Social Winter of Code 2026.
Next Steps:
Happy contributing! 🚀
AvishkarPatil commentedon Jan 3, 2026
Hey @SrishtiSonam , Valid issue - accepted! This is important for production reliability, but please prioritize after rate limiting (#66) is implemented.