[Test] [Issue- 221] : Add unit test for ChatBot #291
Merged
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 change includes the setup of mocks for dependencies used in the ChatBot component tests. It mocks the idGenerator, ChatBotContext, ChatBotLoader, and ChatBotContainer to isolate the component being tested and ensure that the tests are not affected by the actual implementations of these dependencies.
Closes #221
What change does this PR introduce?
Please select the relevant option(s).
What is the proposed approach?
Please give a short overview/explanation on the approach taken to resolve the issue(s).
UUID Generation: Mocked idGenerator to return a consistent UUID ("mocked-uuid") using jest.fn().
ChatBot Context: Mocked useChatBotContext hook and ChatBotProvider component to provide controlled context values.
Component Mocks: Mocked ChatBotLoader and ChatBotContainer components to return simple test elements.
Isolation: Ensured ChatBot component tests are isolated from external factors, making tests reliable and focused on the component itself.
Checklist: