test(query): cover connection resource selectors#1974
Conversation
Connection selector cases existed but the main search resource selector loop did not assert connection results, so regressions could pass unnoticed. Assert expected playbook and connection IDs in the shared loop and add name-based connection selector coverage.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR extends the ChangesSearchResourceSelectors Test Coverage
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
✨ Simplify code
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the 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 |
Benchstat (RLS)Base: ✅ No significant performance changes detectedFull benchstat output |
Benchstat (Other)Base: ✅ 1 improvement(s)
Full benchstat output |
Gavel resultsGavel exited with code . |
Connection selector cases existed in the shared resource selector tests, but their expected IDs were not asserted.
Add assertion coverage for connection results in the main loop and include a name-based connection selector case so regressions are caught.
Summary by CodeRabbit