-
Notifications
You must be signed in to change notification settings - Fork 668
Add documentation on how to mock global components #894
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
Labels
Comments
The option you're looking for is Do you have any suggestions for how we can make this clear? Maybe I guide on mocking components and properties? |
Yes, 100%! I was surprised to not see a guide about stubbing components. Thanks! |
I'm removing comments from this issue since they devolved into an argument. The plan is to add a guide to the documentation on stubbing components and mocking properties. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What problem does this feature solve?
When testing components that include globally registered components, the test runner (in this case, Jest) throws warnings asking if the component was registered properly. As far as I can tell, the documentation doesn't explain how to mock global components.
What does the proposed API look like?
N/A
The text was updated successfully, but these errors were encountered: