AutoMocking dependencies in Blazor

[snerte]

I've created a package solving the issue of having to mock unused dependencies in bUnit tests. It's actually a thin wrapper combining bUnit and Moq.AutoMock.

How annoying is it when a new feature is added to some component and existing tests break, while the new dependency isn't even used? I hope this package helps developers creating tests. I was hoping it could be added to the docs.

https://github.com/snerte/bunit.AutoMocker

[egil]

Awesome. Feel free to submit a PR to the docs if you want.

A subsection on this page is probably the right place: https://bunit.dev/docs/providing-input/inject-services-into-components.html

@linkdotnet what so you think?

[linkdotnet]

Sorry. One idea is to have the code (the two classes: AutoMockerServiceProvider) and optionally AutoMockerTestContext directly shown as code, crediting you and your library - so that folks basically can decide which route they wanna choose.

I don't want to discredit your library in any case, please don't understand me wrong. The compactness of the code, makes it just an obvious candidate for this.

[snerte]

Sorry. One idea is to have the code (the two classes: AutoMockerServiceProvider) and optionally AutoMockerTestContext directly shown as code, crediting you and your library - so that folks basically can decide which route they wanna choose.

I don't want to discredit your library in any case, please don't understand me wrong. The compactness of the code, makes it just an obvious candidate for this.

Sounds good, I've created this library to share the idea. You're fee to use it in any way. Let me know if I can help.

[linkdotnet]

If you want you can create a PR that would add that bit to the documentation.

To make it easy for you, we have support for devcontainers, so there is 0 configuration/setup necessary for you.
You can just easily start a container (New with options and maybe select 4 or 8 cores - you have 120 CPU hours for free each month):

This will spin up a VS Code in the browser that has all the .NET versions installed as well as DocFX, which we use to build the documentation.

Via:

And:

You have the documentation up&running. VS Code informs you, that the docs are ready:

[snerte]

Will do, could take a few days 😊

[linkdotnet]

Really appreciated! And no worries - if you need something, let us know!