TEST: Reuse Python test inputs - #24127
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 12 included reviews per hour; 1 remains after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe tests now use module-scoped fixtures for shared pandas and cuDF indexing and reduction inputs. Reduction tests receive explicit dataset or dtype information from fixture-generated inputs. ChangesTest fixture refactor
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to This change only reorganizes existing test setup code to share read-only test data through fixtures, with no changes to production behavior. Verification confirmed the reduction test's updated expected-failure matching still targets the same cases as before, and the shared fixtures are not mutated by the tests that consume them. This is safe to merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Description
Reuses read-only test data across indexing and reduction tests, avoiding repeated device allocations and conversions while preserving the existing assertions and parameter coverage.
Checklist