Add packages input for selective package testing#9
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughAdds a new 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
4284776 to
c3aed58
Compare
Add a new `packages` input that accepts a multi-line list of package names to test. When provided, uses `-p <pkg>` flags instead of `--all`, allowing selective testing of specific packages. This solves the issue where --exclude doesn't prevent compilation of excluded packages as dependencies, which is problematic when packages have mutually exclusive features. Changes: - Add `packages` input parameter - Update tarpaulin, cargo test, and cross test commands - Add test workflow with fixture workspace
c3aed58 to
f816ecd
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v1-master #9 +/- ##
==============================
==============================
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Adds a
packagesinput to allow testing specific packages instead of the entire workspace.Problem
When using
--excludewith cargo tarpaulin/workspace commands, excluded packages are still compiled as dependencies of included packages. This causes issues when packages have mutually exclusive features (e.g., async vs blocking).Solution
New
packagesinput accepts a multi-line list of package names:When provided, the action uses
-p <pkg>flags instead of--all.Testing
.github/workflows/test-packages-input.ymlwith a fixture workspace undertests/fixtures/packages-input-workspaceBackward Compatibility
When
packagesis empty (default), behavior is unchanged (uses--all).