test(policy): add TPP denial contract proof - #1684
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
✅ Deploy Preview for stranske-trip-planner canceled.
|
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 53 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis change adds end-to-end coverage for importing a failing TPP policy verdict. The test creates an isolated workspace, imports a modified policy fixture, and verifies the non-compliant result and its failure details. ChangesTPP policy import
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/integrations/test_tpp_policy_import.py`:
- Around line 37-44: Add status_code == 201 assertions with response.text to the
signup and trip creation responses in the test setup before yielding the client
or extracting trip_id. Update the relevant setup flow around the client fixture
and trip payload while preserving the existing successful-response behavior.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3e08c23c-3dae-42f2-9c8d-7bf1e4085f1e
📒 Files selected for processing (1)
tests/integrations/test_tpp_policy_import.py
Address CodeRabbit review: include response.text on setup status checks before extracting trip_id in the TPP denial contract proof test. Co-authored-by: Cursor <cursoragent@cursor.com>
Closer review repair (cursor)Addressed the active CodeRabbit thread on setup response assertions:
Validation: Pushed |
Provider Comparison ReportProvider Summary
📋 Full Provider Details (click to expand)openai
anthropic
Agreement
Disagreement
Unique Insights
🔍 LangSmith Traces |
|
Workflow state fingerprint for Agents Verifier. Do not edit. |
Closer verifier disposition (cursor)Audited the durable provider-comparison report on merged #1684 against current OpenAI ( Anthropic ( Review threads: 0 active non-outdated threads on merged head Disposition: Follow-up chain for #1676 is complete. No additional bounded follow-up PR is warranted. Closer emits |
Follow-up for #1676
Addresses the verifier completion-evidence gap on merged #1682.
tests/integrations/test_tpp_policy_import.py::test_failing_policy_status_is_not_compliantcontract test.policy_status=failsnapshot through the workspace import API and asserts the preservedBUD-001blocking reason.policy_status == failbranch temporarily disabled, this exact test fails (compliantinstead ofnon_compliant); restoring the mapping makes the focused suite pass.Validation
uv run ruff check tests/integrations/test_tpp_policy_import.pyuv run ruff format --check tests/integrations/test_tpp_policy_import.pyuv run --extra dev pytest -q tests/integrations/test_tpp_policy_import.py::test_failing_policy_status_is_not_compliant tests/app/test_policy.py::test_workspace_policy_import_maps_tpp_failure_to_blocking_reasons tests/app/test_policy.py::test_workspace_policy_import_surfaces_live_tpp_unavailable_errorsSummary by CodeRabbit