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

   # Which issue does this PR close?
   
   Part of #10540.
   
   # Rationale for this change
   
   Continue consolidating Arrow/Parquet roundtrip coverage in the writer 
integration suite so related end-to-end tests are easier to find and extend. 
Sharing the existing harness allows the tests to move in small batches while 
the remaining unit tests keep using the same validation logic.
   
   # What changes are included in this PR?
   
   - Move 31 tests from the writer's unit test module into 
`parquet/tests/arrow_writer/roundtrip.rs`: 10 numeric, 14 temporal, and 7 
binary/string tests.
   - Extract the existing roundtrip helpers into a test-only module shared by 
unit and integration tests. No public library API or feature is added.
   - Preserve the test bodies, assertions, 
encoding/dictionary/writer-version/row-group combinations, and Miri 
annotations. The integration module temporarily expects unused helpers because 
only part of the suite has moved.
   
   # Are these changes tested?
   
   - `cargo test --locked --offline -p parquet --lib 
arrow::arrow_writer::tests::`: 106 passed.
   - `cargo test --locked --offline -p parquet --test arrow_writer`: 58 passed.
   - `cargo test --locked --offline -p parquet --no-default-features --features 
arrow --test arrow_writer`: 58 passed.
   - `cargo fmt --all --check`
   - `cargo clippy --locked --offline -p parquet --all-targets --all-features 
-- -D warnings`
   
   The affected writer suites still contain 164 tests in total: 137 + 27 before 
migration, 106 + 58 after migration.
   
   # Are there any user-facing changes?
   
   No. This PR reorganizes tests only.
   


-- 
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