docs: fix code references, added missing samples

Author: egil

docs/samples/.editorconfig

@@ -3,6 +3,8 @@ root = true
 [*]
 indent_style = space
 tab_size = 2
+indent_size = 2
+indent_width = 2
 charset = utf-8
 trim_trailing_whitespace = true
 insert_final_newline = false
@@ -13,6 +15,8 @@ trim_trailing_whitespace = false
 [*.{cs,razor}]
 tab_size = 2
 indent_style = space
+indent_size = 2
+indent_width = 2
 dotnet_diagnostic.BL0001.severity = none
 dotnet_diagnostic.BL0002.severity = none
 dotnet_diagnostic.BL0003.severity = none

docs/samples/tests/mstest/HelloWorldExplicitContextTest.cs

@@ -0,0 +1,21 @@
+using Microsoft.VisualStudio.TestTools.UnitTesting;
+using Bunit;
+
+namespace Bunit.Docs.Samples;
+
+[TestClass]
+public class HelloWorldExplicitContext
+{
+  [TestMethod]
+  public void HelloWorldComponentRendersCorrectly()
+  {
+    // Arrange
+    using var ctx = new Bunit.TestContext();
+
+    // Act
+    var cut = ctx.RenderComponent<HelloWorld>();
+
+    // Assert
+    cut.MarkupMatches("<h1>Hello world from Blazor</h1>");
+  }
+}

docs/samples/tests/nunit/HelloWorldExplicitContextTest.cs

@@ -0,0 +1,20 @@
+using Bunit;
+using NUnit.Framework;
+
+namespace Bunit.Docs.Samples;
+
+public class HelloWorldExplicitContext
+{
+  [Test]
+  public void HelloWorldComponentRendersCorrectly()
+  {
+    // Arrange
+    using var ctx = new Bunit.TestContext();
+
+    // Act
+    var cut = ctx.RenderComponent<HelloWorld>();
+
+    // Assert
+    cut.MarkupMatches("<h1>Hello world from Blazor</h1>");
+  }
+}

…tests/xunit/HelloWorldExplicitContext.cs …s/xunit/HelloWorldExplicitContextTest.csdocs/samples/tests/xunit/HelloWorldExplicitContext.cs renamed to docs/samples/tests/xunit/HelloWorldExplicitContextTest.cs docs/samples/tests/xunit/HelloWorldExplicitContext.cs renamed to docs/samples/tests/xunit/HelloWorldExplicitContextTest.cs

@@ -13,7 +13,7 @@ Rendering a component happens through bUnit's <xref:Bunit.TestContext>. The resu
 
 ## Write tests in `.cs` or `.razor` files
 
-bUnit works with MSTest, NUnit, and xUnit, and it allows you to write the unit tests in either `.cs` or `.razor` files. 
+bUnit works with MSTest, NUnit, and xUnit, and it allows you to write the unit tests in either `.cs` or `.razor` files.
 
 The latter, writing tests in `.razor` files, provides an easier way to declare component markup and HTML markup in the tests, so it will most likely be the go-to for many people in the future.
 
@@ -26,8 +26,8 @@ The following sections show how to get started writing tests in either `.cs` or
 Before writing tests in `.razor` files, a few things needs to be in place:
 
 1. Make sure the test project has the SDK type set to `Microsoft.NET.Sdk.Razor`. Otherwise the Blazor compiler will not translate your `.razor` files into runnable code.
-2. Add an `_Imports.razor` file to the test project. It serves the same purpose as `_Imports.razor` files in regular Blazor projects. These using statements are useful to add right away:   
-   
+2. Add an `_Imports.razor` file to the test project. It serves the same purpose as `_Imports.razor` files in regular Blazor projects. These using statements are useful to add right away:
+
    ```cshtml
    @using Microsoft.AspNetCore.Components.Forms
    @using Microsoft.AspNetCore.Components.Web
@@ -37,7 +37,7 @@ Before writing tests in `.razor` files, a few things needs to be in place:
    @using Bunit
    @using Bunit.TestDoubles
    ```
-    
+
 Also add an using statement for your general purpose testing framework, e.g. `@using Xunit` for xUnit.
 
 With that in place, lets look at a simple example that tests the following `<HelloWorld>` component:
@@ -180,22 +180,22 @@ Just be aware that all examples in the rest of the documentation assumes that yo
 
 # [xUnit](#tab/xunit)
 
-[!code-csharp[HelloWorldExplicitContextTest.cs](../../../samples/tests/xunit/HelloWorldExplicitContextTest.cs#L3-L20)]
+[!code-csharp[HelloWorldExplicitContextTest.cs](../../../samples/tests/xunit/HelloWorldExplicitContextTest.cs#L6-L20)]
 
 # [NUnit](#tab/nunit)
 
-[!code-csharp[HelloWorldExplicitContextTest.cs](../../../samples/tests/nunit/HelloWorldExplicitContextTest.cs#L3-L20)]
+[!code-csharp[HelloWorldExplicitContextTest.cs](../../../samples/tests/nunit/HelloWorldExplicitContextTest.cs#L6-L20)]
 
 > [!NOTE]
-> `TestContext` is an ambiguous reference - it could mean `Bunit.TestContext` or `NUnit.Framework.TestContext` - so you have to specify the `Bunit` namespace when referencing `TestContext` to resolve the ambiguity for the compiler. Alternatively, you can give bUnit's `TestContext` a different name during import, e.g.: `using BunitTestContext = Bunit.TestContext;` 
+> `TestContext` is an ambiguous reference - it could mean `Bunit.TestContext` or `NUnit.Framework.TestContext` - so you have to specify the `Bunit` namespace when referencing `TestContext` to resolve the ambiguity for the compiler. Alternatively, you can give bUnit's `TestContext` a different name during import, e.g.: `using BunitTestContext = Bunit.TestContext;`
 
 # [MSTest](#tab/mstest)
 
-[!code-csharp[HelloWorldImplicitContextTest.cs](../../../samples/tests/mstest/HelloWorldExplicitContextTest.cs#L3-L20)]
+[!code-csharp[HelloWorldImplicitContextTest.cs](../../../samples/tests/mstest/HelloWorldExplicitContextTest.cs#L6-L21)]
 
 > [!NOTE]
-> `TestContext` is an ambiguous reference - it could mean `Bunit.TestContext` or `Microsoft.VisualStudio.TestTools.UnitTesting.TestContext` - so you have to specify the `Bunit` namespace when referencing `TestContext` to resolve the ambiguity for the compiler. Alternatively, you can give bUnit's `TestContext` a different name during import, e.g.:   
-> `using BunitTestContext = Bunit.TestContext;` 
+> `TestContext` is an ambiguous reference - it could mean `Bunit.TestContext` or `Microsoft.VisualStudio.TestTools.UnitTesting.TestContext` - so you have to specify the `Bunit` namespace when referencing `TestContext` to resolve the ambiguity for the compiler. Alternatively, you can give bUnit's `TestContext` a different name during import, e.g.:
+> `using BunitTestContext = Bunit.TestContext;`
 
 ## Further reading
 

docs/site/docs/getting-started/writing-tests.md

@@ -7,11 +7,11 @@ title: Triggering a render life cycle on a component
 
 To trigger a re-render of a component under test, a reference to it through a <xref:Bunit.IRenderedComponent`1> type is needed. When using the <xref:Bunit.TestContext>'s `RenderComponent<TComponent>()` method, this is the type returned.
 
-In `.razor` based tests, using the <xref:Bunit.TestContext>'s <xref:Bunit.TestContext.Render``1(RenderFragment)> method also returns an <xref:Bunit.IRenderedComponent`1> (as opposed to the <xref:Bunit.TestContext.Render(RenderFragment)> method which returns the more simple <xref:Bunit.IRenderedFragment>). 
+In `.razor` based tests, using the <xref:Bunit.TestContext>'s <xref:Bunit.TestContext.Render``1(RenderFragment)> method also returns an <xref:Bunit.IRenderedComponent`1> (as opposed to the <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> method which returns the more simple <xref:Bunit.IRenderedFragment>).
 
 If you have a <xref:Bunit.IRenderedFragment> or a <xref:Bunit.IRenderedComponent`1> in a test, but need a child component's <xref:Bunit.IRenderedComponent`1>, then use the `FindComponent<TComponent>()` or the `FindComponents<TComponent>()` methods, which traverse down the render tree and finds rendered components.
 
-With a <xref:Bunit.IRenderedComponent`1>, it is possible to cause the component to render again directly through the [`Render()`](xref:Bunit.RenderedComponentRenderExtensions.Render``1(Bunit.IRenderedComponentBase{``0})) method or one of the [`SetParametersAndRender()`](xref:Bunit.RenderedComponentRenderExtensions.SetParametersAndRender``1(Bunit.IRenderedComponentBase{``0},System.Action{Bunit.ComponentParameterCollectionBuilder{``0}})) methods, or indirectly through the [`InvokeAsync()`](xref:Bunit.IRenderedFragmentBase.Bunit.RenderedFragmentInvokeAsyncExtensions.InvokeAsync(System.Action)) method.
+With a <xref:Bunit.IRenderedComponent`1>, it is possible to cause the component to render again directly through the [`Render()`](xref:Bunit.TestContext.Render``1(Microsoft.AspNetCore.Components.RenderFragment)) method or one of the [`SetParametersAndRender()`](xref:Bunit.RenderedComponentRenderExtensions.SetParametersAndRender``1(Bunit.IRenderedComponentBase{``0},System.Action{Bunit.ComponentParameterCollectionBuilder{``0}})) methods, or indirectly through the [`InvokeAsync()`](xref:Bunit.IRenderedFragmentBase.Bunit.RenderedFragmentInvokeAsyncExtensions.InvokeAsync(System.Action)) method.
 
 Let's look at how to use each of these methods to cause a re-render.
 
@@ -21,7 +21,7 @@ The [`Render()`](xref:Bunit.RenderedComponentRenderExtensions.Render``1(Bunit.IR
 
 [!code-csharp[](../../../samples/tests/xunit/ReRenderTest.cs?start=17&end=23&highlight=5)]
 
-The highlighted line shows the call to [`Render()`](xref:Bunit.RenderedComponentRenderExtensions.Render``1(Bunit.IRenderedComponentBase{``0})). 
+The highlighted line shows the call to [`Render()`](xref:Bunit.RenderedComponentRenderExtensions.Render``1(Bunit.IRenderedComponentBase{``0})).
 
 > [!TIP]
 > The number of renders a component has been through can be inspected and verified using the <xref:Bunit.IRenderedFragmentBase.RenderCount> property.