test(core): strengthen error unit test coverage#827
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Motivation
Error-related unit tests more focused and actionable by verifying bothDisplayoutput and currentsource()semantics for each variant.Description
error_messages_are_readabletest into three focused tests:missing_env_var_message_is_readable,invalid_seed_message_is_readable, andio_error_variant_preserves_inner_error.use std::error::Error as _;and explicitsource()assertions to lock in the current error-chaining semantics (non-IO variants and the current IO conversion return nosource).Io(#[from] std::io::Error)conversion.Testing
cargo test -p uselesskey-core error::tests --features stdand verified3 passed; 0 failedfor the targeted tests.Codex Task