Phoenix500526 opened a new pull request, #12362:
URL: https://github.com/apache/arrow-rs/pull/12362

   # Which issue does this PR close?
   
   Part of #12328.
   
   # Rationale for this change
   
   Several Parquet tests bury independent scenarios in nested loops. 
Parameterizing those scenarios makes failures easier to identify and reduces 
nesting while keeping data generation and stateful checks together.
   
   # What changes are included in this PR?
   
   - Use `rstest` cases and values for row-selection masks, page boundaries, 
RLE and bit-reader operations, definition levels, Bloom filters, metadata 
updates, and data-page null counts.
   - Parameterize synchronous and asynchronous legacy fixed-length byte-array 
reads and asynchronous row filtering.
   - Separate dictionary-capacity success from overflow, and isolate zero-width 
and empty-buffer checks.
   - Add `rstest` as a development dependency, with its default features 
disabled.
   
   # Are these changes tested?
   
   The refactoring preserves the existing input combinations, assertions, 
seeded random data, feature gates, and Miri exclusions. Dependent and stateful 
loops remain inside the tests, including skip/read/EOF sequences and row-group 
traversal.
   
   Local validation with async and encryption enabled passed 2,004 unit tests 
and 236 arrow-reader integration tests, with one existing ignored test in each 
suite. Relevant Clippy, formatting, and spelling checks also passed. Miri was 
not run.
   
   # Are there any significant user-facing changes?
   
   No. Production code and public APIs are unchanged.
   
   # AI usage disclosure
   
   Codex helped identify candidates, generate and review test refactoring, and 
run validation. The changes were developed and reviewed interactively with the 
author.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to