test: Add unit test for projects/app/src/components/core/chat/ChatContainer/utils.ts #6218
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.
Trigger Info
Summary
This PR introduces unit tests for the
groupChatItemsByDeleteStatusutility function in theChatContainercomponent. The tests cover various scenarios to ensure the function correctly groups chat items based on their delete status.Key Changes:
Test Cases Added:
Empty input returns an empty array.
All normal items are grouped together.
All deleted items are grouped together.
Alternating normal and deleted items are grouped correctly.
Single normal item is handled correctly.
Single deleted item is handled correctly.
Interleaved normal and deleted items are grouped correctly.
Items with
deleteTime=0are treated as normal.Items with
deleteTime=nullorundefinedare treated as normal.Test Coverage:
Ensures the function handles edge cases like empty arrays, single items, and interleaved items.
Validates the behavior for different
deleteTimevalues, including0,null, andundefined.These tests ensure the robustness and reliability of the
groupChatItemsByDeleteStatusfunction in handling various input scenarios.Coverage
The change in coverage value, such as:
0% -> 50%, indicates that the coverage was 0% before writing the tests and 50% after writing them.https://web.dev/articles/ta-code-coverage
Test Statuses
Tip
You can
@gru-agentand leave your feedback. TestGru will make adjustments based on your inputTip
You can
@gru-agent rebaseto rebase the PR.Tip
You can
@gru-agent redoto reset or rebase before redoing the PR.Tip
To modify the test code yourself, click here Edit Test Code