-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Add Potential issues with Jest testing
React docs section
#17032
Conversation
Is |
9a5e14d
to
2ac8dcc
Compare
@godai78 rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some suggestions.
As we removed jest-pupeeter let's maybe say what, we think, is right: |
@Witoso Good idea, I'll adjust a bit docs. |
@Witoso done |
Suggested merge commit message (convention)
Docs: Add
Potential issues with Jest testing
section to React integration docs.Additional information
Related to ckeditor/ckeditor5-react#225
I added this section to address the increasing number of reports regarding issues with Jest testing in React applications. This explanation clarifies the limitations of Jest when used with CKEditor 5 and provides a solution for more accurate testing by using jest-puppeteer or a mock snippet.