-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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: Update .toHaveBeenCalled() documentation #14847
Conversation
Updated .toHaveBeenCalled name and description. Its description now correctly reflects that it is not called with any arguments.
Updated .toHaveBeenCalled name and description. Its description now correctly reflects that it is not called with any arguments.
Updated .toHaveBeenCalled name and description. Its description now correctly reflects that it is not called with any arguments.
Updated .toHaveBeenCalled name and description. Its description now correctly reflects that it is not called with any arguments.
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Updated changelog entry to be more reflective of change.
Updated with more specific documentation change descriptions in changelog.
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.
thanks!
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
This change concerns issue #14842, where .toHaveBeenCalled() and .toHaveBeenCalledWith() have duplicate descriptions despite serving two different functionalities. I made this change because .toHaveBeenCalled() refers to an example where there are no function parameters, and therefore should be updated accordingly because it was not called with specific arguments. Therefore, I took out the argument explanations and simply revised the description to correctly reflect
.toHaveBeenCalled
's functionality.I additionally updated the descriptions for all versioned docs which concern this documentation issue.
Fixes #14842
Test plan
By updating the documentation, I then ran it on the documentation website node server to make sure changes were updated accordingly. Jest documentation versions 29.7, 29.6, 29.5, and 29.4 were changed.
Documentation on the server now showing corrected values.