test: split bounty API route coverage#416
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis PR reorganizes bounty API multi-award tests by consolidating them from ChangesBounty API Multi-Award Tests Migration
Possibly related PRs
Suggested labels
Suggested reviewers
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Reviewed the split against Bounty #410 and the current PR head No blockers from my pass. The change is test-organization only: the multi-award bounty API route coverage is moved out of Validation run locally in a clean review worktree after installing the project-declared dev dependencies from
|
Summary
tests/test_api_mcp.pyinto focusedtests/test_bounty_api_routes.py.Evidence
Preflight before submission: MRWK bounty API showed issue #410 open with
awards_remaining=3; GitHub issue #410 was open. Existing open PR #415 also targets #410, but it splits security URL validation tests, so this is a distinct test-module split fromtests/test_api_mcp.py.Validation
./.venv/bin/python -m pytest tests/test_bounty_api_routes.py tests/test_api_mcp.py -q-> 81 passed./.venv/bin/python -m pytest -q-> 377 passed./.venv/bin/python -m ruff check .-> passed./.venv/bin/python -m ruff format --check .-> passed./.venv/bin/python -m mypy app-> passedgit diff --check-> cleanSummary by CodeRabbit