Mock a component with named ref and injected service

[ProsperoTheBun]

It's mentioned in the documentation that when testing component Foo that consumes a component Bar when the component Bar has an @ref=bar attribute, that we can write a subclass MockBar or use Moq as a substitute. That's great and works fine.

But what should I do when Bar has an injected service? Say, IWibbleService.

The only way I can get it to work is by adding a Mock<IWibbleService>().Object to the DI container in the Foo test. This feels like an anti-pattern in that my test of Foo shouldn't care about the dependencies of Bar.

I've tried hacking various solutions including making the IWibbleService a virtual property of Bar and overriding it in a subclass but I'm not getting anywhere.

[linkdotnet]

Sorry for being a bit late - while I do understand the issue, it depends (of course, as always :D ) what your target is.

If <Bar> is part of your component tree and you need the concrete <Bar> you have to provide a Service.
But we give you basically the option to stub or fake out the whole component. So given you have something like this:

<Foo>
 <Bar/>
<Foo>

You can do the following:

ComponentFactories.AddStub<Bar>();

This would remove Bar entirely and replaced it with an empty markup. Here some further information: https://bunit.dev/docs/providing-input/substituting-components.html?q=Stub&tabs=moq

We also offer an experimental source code generator, that does what is described above but also mimicks the public parameter surface of your component: https://bunit.dev/docs/extensions/bunit-generators.html?q=Stub