Add Unit tests for userFlowInternal Hook #206
Merged
Conversation
This file contains 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
|
@tjtanjin could u review PR and let me know feedback..Thank YOU :) |
RAVEYUS
pushed a commit
to RAVEYUS/react-chatbotify
that referenced
this pull request
Nov 2, 2024
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.
Description
This update introduces unit tests for the useFlowInternal hook, covering various scenarios such as retrieving initial context values, handling the flow state, and ensuring proper behavior of the restartFlow functionality. These tests aim to increase the reliability of the hook by verifying its interaction with contexts like MessagesContext, PathsContext, ToastsContext, BotRefsContext, and BotStatesContext.
Issue: [Task] Add unit test cases for useFlowInternal hook #129
Closes #129
What change does this PR introduce?
Please select the relevant option(s).
What is the proposed approach?
The proposed approach involves mocking the relevant contexts used within the useFlowInternal hook, then utilizing the @testing-library/react renderHook and act functions to simulate real usage scenarios.
Checklist: