Expand backend API contract edge-case tests#13
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Status refresh for review: This PR is still current for bounty issue #1 and remains ready for review. The focused backend API contract suite passed locally (15 passed), and the PR body includes the Windows build.py diagnostic JSON explaining why the encrypted .logd artifact could not be produced in this environment. Please let me know if any final change is needed before acceptance or bounty payment review. Payment address: 0x1aba67a6f349826fbaea17f54556a42d42399474 |
Summary
Closes #1
Expands backend API contract edge-case coverage and makes the offline mock client return structured validation errors for missing request bodies, missing required fields, and malformed field types.
Changes
asyncio.run, so the suite does not require optional pytest async plugins.tests/backend_api/README.md.diagnostic/build-011bb3d4.json, generated bybuild.pyafter the repo encryptly preflight failed on this Windows environment.Testing
.\.venv\Scripts\python.exe -m pytest -q tests\backend_api-> 15 passed..\.venv\Scripts\python.exe -m py_compile backend\api_contract.py tests\conftest.py tests\backend_api\test_openapi_contract.py-> passed.python build.py-> failed during encryptly preflight before module builds; it generateddiagnostic/build-011bb3d4.jsonexplaining why no encrypted.logdwas created.Checklist
Bounty payout address: 0x1aba67a6f349826fbaea17f54556a42d42399474