test(ci): lint integration-tagged files and reduce test complexity#13
Conversation
golangci-lint, go vet, and go test skip files behind //go:build integration by default, so integration_test.go was never linted — hiding gocyclo warnings (complexity 20 > 15) in TestIntegration_BatchPublishAndClearConcurrent and TestIntegration_AnonymousQueueReconnect. - Pass --build-tags=integration to golangci-lint in both the Makefile and the CI lint job so integration tests are linted (and type-checked) going forward. - Extract reusable helpers (recvDelivery, waitForReDeclaredQueue, publishUntilDelivered, collectUniqueMessages) to bring both functions under the complexity threshold; behavior is unchanged. Verified: lint clean in both default and integration modes; full integration suite passes against RabbitMQ 4.3.2.
|
Warning Review limit reached
Next review available in: 16 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ 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 |
golangci-lint, go vet, and go test skip files behind //go:build integration by default, so integration_test.go was never linted — hiding gocyclo warnings (complexity 20 > 15) in TestIntegration_BatchPublishAndClearConcurrent and TestIntegration_AnonymousQueueReconnect.
Verified: lint clean in both default and integration modes; full integration suite passes against RabbitMQ 4.3.2.
Summary
Motivation
Fixes #
Changes
Checklist
make all)