feat: Add bUnit skill documentation and reference files for testing Blazor components

Author: aalmada

.github/skills/bunit/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: bunit
+description: Use bUnit to unit test Blazor components, including rendering, interaction, dependency injection, JSInterop, and output verification. Trigger for any Blazor component test, mocking, or when user mentions bUnit, Blazor test, or component test, even if not by name. Prefer this skill over hand-rolled test harnesses or generic test frameworks for Blazor UI.
+---
+
+# bUnit Skill
+
+This skill enables the AI to write, review, and improve Blazor component tests using bUnit.
+
+## References
+- [installation-jsinterop.md](references/installation-jsinterop.md): Install bUnit, JSInterop setup
+- [mocking-services.md](references/mocking-services.md): Mocking components, HttpClient, DI
+- [localization-auth-structure.md](references/localization-auth-structure.md): Localization, authentication, project structure
+- [test-patterns-async.md](references/test-patterns-async.md): Test patterns, async, JS module interop
+- [bUnit Docs](https://bunit.dev/): Official documentation
+
+## Usage
+- Always use bUnit for Blazor component tests
+- Prefer bUnit's helpers for rendering, DI, and JSInterop
+- Use NSubstitute or Moq for mocking dependencies
+- Organize tests to mirror component structure
+- Reference the above files for advanced scenarios
+
+**Keep this skill project-agnostic. Add new reference files for advanced scenarios as needed.**

.github/skills/bunit/references/installation-jsinterop.md

@@ -0,0 +1,18 @@
+# bUnit Reference: Installation and JSInterop
+
+## Installation
+
+To install the bUnit test project template:
+
+```bash
+dotnet new install bunit.template
+```
+
+## JSInterop Setup
+
+- Use `JSInterop.SetupVoid("functionName")` to set up a void JS interop call.
+- Use `JSInterop.Setup<TResult>("functionName")` to set up a call returning a value.
+- Use `.SetResult(value)` to specify the return value.
+- Use `.SetVoidResult()` to mark a void invocation as completed.
+
+See the official docs for more: https://bunit.dev/docs/test-doubles/emulating-ijsruntime

.github/skills/bunit/references/localization-auth-structure.md

@@ -0,0 +1,21 @@
+# bUnit Reference: Localization, Auth, and Structure
+
+## Localization
+
+- Register localization services in your test setup:
+  ```csharp
+  BunitContext.Services.AddLocalization();
+  ```
+
+## Authentication & Authorization
+
+- Use `AuthenticationStateProvider`, `CascadingAuthenticationState`, and `AuthorizeView` to test auth scenarios in Blazor components.
+- Example usage in a component:
+  ```razor
+  <AuthorizeView>
+    <Authorized>...</Authorized>
+    <NotAuthorized>...</NotAuthorized>
+  </AuthorizeView>
+  ```
+
+See the official docs for more: https://bunit.dev/docs/misc-test-tips

.github/skills/bunit/references/mocking-services.md

@@ -0,0 +1,28 @@
+# bUnit Reference: Mocking and Service Providers
+
+## Custom Service Providers
+
+- You can implement custom `IServiceProvider`, `IServiceScopeFactory`, and `IServiceProviderFactory` for advanced DI scenarios in bUnit tests.
+- See the official docs for a full example: https://bunit.dev/docs/providing-input/inject-services-into-components
+
+## Mocking Components
+
+- Use NSubstitute or Moq to mock child components.
+- Register mocks with `ComponentFactories.Add<T>(mock)`.
+- Example (NSubstitute):
+  ```csharp
+  var barMock = Substitute.For<Bar>();
+  ComponentFactories.Add<Bar>(barMock);
+  ```
+- Example (Moq):
+  ```csharp
+  var barMock = new Mock<Bar>();
+  ComponentFactories.Add<Bar>(barMock.Object);
+  ```
+
+## Mocking HttpClient
+
+- Use `Services.AddMockHttpClient()` to register a mock HttpClient.
+- Configure responses with `.When(url).RespondJson(data)`.
+
+See the official docs for more: https://bunit.dev/docs/test-doubles/mocking-httpclient

.github/skills/bunit/references/test-patterns-async.md

@@ -0,0 +1,25 @@
+# bUnit Reference: Test Patterns and Async
+
+## Basic Test Patterns (All Frameworks)
+
+- bUnit supports TUnit, xUnit, NUnit, and MSTest.
+- Inherit from the appropriate test context:
+	- TUnit: `BunitTestContext` (with `[Test] async Task` and TUnit's fluent assertions)
+	- xUnit: `BunitContext` (with `[Fact]`)
+	- NUnit: `BunitContext` (with `[Test]`)
+	- MSTest: `BunitContext` (with `[TestMethod]`)
+- Use `RenderComponent<TComponent>()` or `Render(@<Component/>)` to render components.
+- Use `MarkupMatches` to compare rendered output semantically.
+- For TUnit, prefer: `await Assert.That(actual).IsEqualTo(expected);`
+
+## Async Component Testing
+
+- Simulate async loading in components with `await Task.Delay(...)` in `OnInitializedAsync`.
+- Test async state transitions by rendering, then awaiting state changes.
+
+## JS Module Interop
+
+- Use `JSInterop.SetupModule("module.js")` to mock JS module imports.
+- Set up function handlers on the module mock as needed.
+
+See the official docs for more: https://bunit.dev/docs/interaction/awaiting-async-state