Add circular_dynamic_buffer wrapping, boundary, and fuzz tests#201
Add circular_dynamic_buffer wrapping, boundary, and fuzz tests#201sgerbino merged 1 commit intocppalliance:developfrom
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
|
An automated preview of the documentation is available at https://201.capy.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-03-04 17:56:42 UTC |
|
GCOVR code coverage report https://201.capy.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-03-04 18:09:38 UTC |
Cover code paths the existing testMembers/testGrind harness cannot reach: two-segment buffer splits when data wraps around the ring, clamping behavior for oversized commit/consume, the in_pos_ reset optimization in consume(), capacity-1 boundary, and a 2000-iteration fuzz test against a reference model.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #201 +/- ##
===========================================
+ Coverage 91.77% 91.95% +0.17%
===========================================
Files 76 76
Lines 4500 4500
===========================================
+ Hits 4130 4138 +8
+ Misses 370 362 -8 see 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Cover code paths the existing testMembers/testGrind harness cannot reach: two-segment buffer splits when data wraps around the ring, clamping behavior for oversized commit/consume, the in_pos_ reset optimization in consume(), capacity-1 boundary, and a 2000-iteration fuzz test against a reference model.