-
Notifications
You must be signed in to change notification settings - Fork 668
findAllComponents() is not a proper substitute for findAll() #1594
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
Comments
Hi! As stated in Update docs, you can use So it is likely that Hope it helps! |
Hi! The deprecation warning is only about using |
Well that make sense, I forgot to distinguish between these two, sometimes my brain needs a little kick in in the ass. Thank you for your help. |
Why do the docs here state that you can pass a selector to https://v1.test-utils.vuejs.org/api/wrapper/findallcomponents.html |
Feature Description
wrapper.findAllComponents()
should Take CSS selectors as an argument.Well maybe I'm doing something wrong by not throwing refs on every tiny element in my component or making sub components out of every div, but how can I safely test the amount of elements rendered to a list by referencing their
class
selector when I should not be using the findAll() method anymore?Am I missing something (which is definitely not unlikely)? If not, this feature would be well appreciated.
Problem
wrapper.findAll()
Has a deprecation warning, the suggested substitutewrapper.findAllComponents()
does not cover the functionality.Expected behaviour
As described in the Feature Description
Alternatives
An additional
wrapper.findAllElements()
function.The text was updated successfully, but these errors were encountered: