🧪 [testing improvement] Add missing tests for check_summary in pr_review_autofix_context.py

[seonghobae]

🎯 What: Added tests for the previously untested check_summary function in scripts/ci/pr_review_autofix_context.py.
📊 Coverage: Covered all node parsing scenarios including: empty inputs, complete CheckRun fields, missing name, missing workflowName, missing both, StatusContext types, and unknown/graceful fallback nodes.
✨ Result: 100% code coverage on check_summary with deterministic assertions validating format and formatting regressions.

---

PR created automatically by Jules for task 7590042593689723795 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 8f7a424d-8503-4a1c-84e3-0603efa532ec

📥 Commits

Reviewing files that changed from the base of the PR and between 6eb06cd and 1ee7278.

📒 Files selected for processing (1)

• tests/test_pr_review_autofix_context_check_summary.py

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

RCA/feasibility: closing as redundant with the authoritative source-changing/coverage branch. PR #782 changes pr_review_autofix_context.py and already verifies the complete production module at 215/215 statements and 92/92 branches, including the check-summary path, on its exact head. This PR adds a second isolated current-main test lane for one helper but changes no production defect and would need reconciliation after #782. Keep coverage ownership with the branch that changes the implementation rather than multiplying review/check work.

[google-labs-jules]

RCA/feasibility: closing as redundant with the authoritative source-changing/coverage branch. PR #782 changes pr_review_autofix_context.py and already verifies the complete production module at 215/215 statements and 92/92 branches, including the check-summary path, on its exact head. This PR adds a second isolated current-main test lane for one helper but changes no production defect and would need reconciliation after #782. Keep coverage ownership with the branch that changes the implementation rather than multiplying review/check work.

Understood. Acknowledging that this work is now redundant with PR #782 and stopping work on this task.