If the component that you are searching is being rendered by a stub, ofc its not going to be found, its not there... That is the idea of the stub, to not render its inner children.

@dobromir-hristov, thanks for the quick response! I think you are misunderstanding my issue. If you look at the tests in the minimal repro, you'll see that the component that I am searching is not being rendered by a stub, but rather is being stubbed itself.

Let me be additionally clear:
component: App
renders Child

component Child
renders Grandchild

When I stub Grandchild, I would expect to be able to find it using wrapper.find.
In fact, you can verify that the stub is being rendered by looking at wrapper.html or find('grandchild-stub') but the find method does not work as expected

I'll edit the issue to make it more clear. Let me know if there's anything else I could explain more clearly!

OK so there are two issues here.

One is that your components are each at the root of the their parent. That may be causing some issues. The current implementation of stubs is pretty nasty.

The problems with props is there I know, alas its not something that may get fixed soon/easily. If we fix it, it will break for allot of people.

Both of these are fixed in VTU 2, that will be out for Vue 3. It has a much simpler, and stable stubs implementation.

@dobromir-hristov
That's an interesting point about components being at root. In the context where I ran into this issue, the component was not at the root level.

In any case, thanks for the response and explanation. I look forward to all the new goodness that Vue 3 and VTU 2 will bring!

For posterity and if anyone else runs into this issue and needs a workaround, here's a jest mock example:

import ComponentName from 'path/to/ComponentName';
jest.mock('path/to/ComponentName', () => ({
  name: 'ComponentName',
  props: ['someProp'], // this is needed in order be able to access the prop
  render() { return null; }
}));

Then you can use wrapper.find as normal!

I think we should be able to allow finding a root node with find pretty easily - if anyone is interested, this should be a good first issue.

VTU next has an implementation you could reference.