Surajsuthar opened a new pull request, #4703:
URL: https://github.com/apache/iggy/pull/4703

   ## Which issue does this PR address?
   
   <!--
   We generally require a GitHub issue for all bug fixes and enhancements. Link 
it with GitHub syntax, keep the line that applies and delete the other:
   - `Closes #123` auto-closes the issue when this PR merges (full fix).
   - `Relates to #123` links without closing (partial or related work).
   -->
   
   Closes #4684 
   Relates to #4684
   
   ## Rationale
   
   Separate tests from implementation as the first step toward refactoring 
core/partitions/
   ## What changed?
   
   - Moved iggy_partition.rs tests into iggy_partition_tests 
(core/partitions/src/iggy_partition_tests).
   - Moved private recovery tests into segment_recovery_tests.rs 
(core/partitions/src/segment_recovery_tests.rs).
   - Moved public segment-recovery tests into tests/segment_recovery.rs 
(core/partitions/tests/segment_recovery.rs).
   - Moved the public state-transfer loader test into tests/state_transfer.rs 
(core/partitions/tests/state_transfer.rs).
   - iggy_partition.rs, segment_recovery.rs, and state_transfer.rs now contain 
implementation plus test-module declarations only.
   - No production visibility changes. Fixtures remain private or pub(super) 
only where internal test modules require them.
   
   
   ## Local Execution
   
   - Passed 
   - Pre-commit hooks ran
   
   <!--
   You must run your code locally before submitting.
   "Relying on CI" is not acceptable - PRs from authors who haven't run the 
code will be closed.
   
   Did you have `prek` installed? It runs automatically on commit and covers 
all project languages. See 
[CONTRIBUTING.md](https://github.com/apache/iggy/blob/master/CONTRIBUTING.md).
   -->
   
   ## AI Usage
    use Codex for grouping of test by their behavior 
   


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