test(core): strengthen proptest coverage and reduce rejects#812
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
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
core_propmodule to detect more edge cases per run by increasing the case count.prop_assume!filters that reject generated examples, making tests more efficient and stable.Description
#![proptest_config(ProptestConfig { cases: 96, ..ProptestConfig::default() })]tocrates/uselesskey-core/tests/core_prop.rsto increase per-run sample counts.prop_assume!(label1 != label2)andprop_assume!(variant1 != variant2)with normalization logic that ensures the second generated value differs (e.g.let label2 = if label1 == label2 { format!("{}x", label2) } else { label2 };).Testing
cargo test -p uselesskey-core --test core_prop, which completed successfully with all tests passing.Codex Task