test: add boundary tests for configuration numeric limits - #1926
emersonbusson wants to merge 1 commit into
Conversation
Added testing coverage for boundary config values (zero capacity, u64::MAX capacity, negative capacity, negative queue depth and non-UTF8 strings). Rollback trigger: tests fail.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Closed in favor of PR #2085 consolidation. |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
1 participant
Summary
Added testing coverage for boundary config values (zero capacity, u64::MAX capacity, negative capacity, negative queue depth and non-UTF8 strings).
Commits
Details
Files:crates/ramshared-winsvc/src/config.rsValidation: Built and tested locally.
Risk/rollback: Tests fail.
Issue
None
Owner
Jules
Labels
type:test,area:ramshared-winsvc
Validation
cargo test -p ramshared-winsvc passed.
Rollback trigger
tests fail.
PR created automatically by Jules for task 11467933058448803237 started by @emersonbusson