Fix argument accumulation bug in integration test#499
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 13 minutes and 18 seconds. ⌛ 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. ✨ 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 |
The test reused a single Command, causing args to accumulate across cases. Each argument-count scenario now uses a fresh Command.
b3efd12 to
738773d
Compare
Summary
test_different_amount_of_argumentsreused a singleCommand, causing.args()to accumulate. The "1 argument" case actually ran with 1 arg, "2 arguments" with 2, and "3 arguments" with 3 — only by accident.Command.Test plan
cargo test --test int_testspasses