You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether it's <FooStub /> or <foo-stub> /> doesn't matter, the point is that the components are no longer rendered, nor is any of their code executed.
Things to consider:
should a user be able to find a stubbed out component? Feels a bit weird to try and find a component that is purposefully NOT rendered. But it might be a common use case
Will probably rely on #9
Instead of
shallowMount
, I think we should have ashallow
mounting option (discussed internally).How this should work
shallowMount
was pretty buggy in VTU beta. It should completely stub out and child components. So:Should render as follows when using
shallow
:Whether it's
<FooStub />
or<foo-stub>
/> doesn't matter, the point is that the components are no longer rendered, nor is any of their code executed.Things to consider:
find
a stubbed out component? Feels a bit weird to try and find a component that is purposefully NOT rendered. But it might be a common use casefind
does not supportfind(Component)
syntax. I'm not sure it should - it was impossiblefind
. One such issue: Some stubbed Vuetify components can't be found withfind
wrapper method vuejs/vue-test-utils#1272 andThe text was updated successfully, but these errors were encountered: