test(team-view): cover column-header sorting in the members heatmap#201
Conversation
The diff-coverage gate on #200 flagged the column-sort branch of sortedRows (COLUMNS.findIndex lookup) — the revert re-introduced those lines and no test clicked a column header. Add a test that sorts by a higher-is-better column, checks the row order flips, and exercises the lower-is-better path with missing values. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Roman Mitasov <roman.mitasov@constructor.tech>
|
Warning Review limit reached
Next review available in: 19 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Problem
The diff-coverage gate failed on #200 (77.8% < 80%): the revert re-introduced the column-sort branch of
sortedRows(COLUMNS.findIndexlookup,index.tsxlines 386–387) as changed lines, and no test clicks a column header, so those lines were uncovered.Change
Add a component test that:
Verified locally: the previously missing lines now report hits in the coverage output, and the full vitest suite passes.
🤖 Generated with Claude Code