Scoped IComponentActivator breaks bUnit

I’m pretty sure the problem reported in the SO question below is due to Blazorise registering a IComponentActivator as scoped, replacing our singleton registered BunitComponentActivator. However, since the WebTestRenderer is registered as a singleton it cannot be resolved.

The fix may be to register the renderer as a scoped service and all other dependent services like this too.

https://stackoverflow.com/questions/76597158/bunit-blazorise-cannot-consume-scoped-service-microsoft-aspnetcore-components

related: #1129

[linkdotnet]

Correct. My understanding is that a scoped service can depend on a singleton service, so I do not expect this would break users. It would solve a problem like the one being reported here, where users have to take extra steps.

Do you see any downsides to us registering all our services as scoped?

Yes, but singleton services can not depend on scoped services. Like the BunitHtmlParser that is a singleton, can not depend on TestRenderer that is a scoped service.

Anyway - making everything scoped would be my preferred anyway. Technically it wouldn’t change much the majority of use cases.

[linkdotnet]

I’ll quote the official Blazorise docs:

For testing purposes, there is currently an internal Blazorise Service that should be configured as Transient so the bUnit test engine does not throw an error. You should add this setup: ctx.Services.AddBlazorise().Replace(ServiceDescriptor.Transient<IComponentActivator, ComponentActivator>());

Other than that it should pretty much work out of the box. Let us know if you’re having any difficulties. For some testing examples, you can look at some of our <Blazorise.Link To=“https://github.com/Megabit/Blazorise/tree/master/Tests/Blazorise.Tests” Target=“Target.Blank”>tests</Blazorise.Link>.

That said, that would help the person in question on SO.