[12.x] Add test for untested methods in LazyCollection #54996
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds test coverage for the before() method including: - Non-strict comparison - Strict comparison - Callback function usage
mohammadrasoulasghari
changed the title
This commit adds test coverage for the shuffle() method including:
mohammadrasoulasghari
force-pushed
the
tests/lazy-collection-tests
branch
from
bd28a1e to
efe7171
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add test coverage for untested methods in LazyCollection
I added test coverage for untested before() and shuffle() methods in LazyCollection class
These methods previously had no test coverage. I implemented comprehensive test cases for both methods:
For before() method:
For shuffle() method:
Each test case covers different edge cases and scenarios to ensure proper functionality and prevent potential side effects during future modifications. The tests validate both simple and complex use cases, ensuring the methods work as expected across different data types and structures. 🛡️