test: strengthen webhook unit coverage#784
Conversation
|
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
Description
crates/uselesskey-webhook/src/lib.rscovering an RFC-style long-key HMAC-SHA256 vector to exercise the key-hashing branch (hmac_sha256_hashes_keys_larger_than_block_size).WebhookPayloadSpec::Rawpayloads are used verbatim for signature inputs for GitHub, Stripe, and Slack (raw_payload_is_used_verbatim_for_signature_inputs).(profile, label, payload_spec)and differ when any element changes (fixture_cache_identity_includes_profile_label_and_payload_spec).StaleTimestamp,WrongSecret,TamperedPayload) and verify provider verification rejects them (near_miss_scenarios_are_marked_and_recomputed_for_each_profile).Testing
cargo test -q -p uselesskey-webhook, which completed successfully (16 passed; 0 failed).cargo clippy -q -p uselesskey-webhook --all-targets -- -D warnings, which completed with no lints reported.Codex Task