docs: fixing broken code references

Author: egil

docs/samples/components/CounterWithFancyParagraph.razor

@@ -0,0 +1,14 @@
+<h1>Counter</h1>
+
+<FancyParagraph Text=@($"Current count: {currentCount}") />
+
+<button class="btn btn-primary" @onclick="IncrementCount">Click me</button>
+
+@code {
+  int currentCount = 0;
+
+  void IncrementCount()
+  {
+    currentCount++;
+  }
+}

docs/samples/components/FancyParagraph.razor

@@ -0,0 +1,5 @@
+<p>@Text</p>
+@code {
+	[Parameter] 
+    public string Text { get; set; }
+}

docs/samples/tests/xunit/CounterWithFancyParagraphTest.cs

@@ -0,0 +1,43 @@
+#if NET5_0_OR_GREATER
+using Xunit;
+using Bunit;
+using Moq;
+using NSubstitute;
+
+namespace Bunit.Docs.Samples
+{
+  public class CounterWithFancyParagraphTest
+  {
+    [Fact]
+    public void CounterShouldIncrementWhenClicked_Moq()
+    {
+      using var ctx = new TestContext();      
+      Mock<FancyParagraph> mock = new Mock<FancyParagraph>();
+      FancyParagraph mockComponent = mock.Object;
+
+      ctx.ComponentFactories.Add(mock.Object);
+        
+      var cut = ctx.RenderComponent<Counter>();
+
+      cut.Find("button").Click();
+
+      cut.Find("p").MarkupMatches("<p>Current count: 1</p>");
+    }
+
+    [Fact]
+    public void CounterShouldIncrementWhenClicked_NSubstitute()
+    {
+      using var ctx = new TestContext();      
+      FancyParagraph mockComponent = Substitute.For<FancyParagraph>();
+
+      ctx.ComponentFactories.Add(mockComponent);
+        
+      var cut = ctx.RenderComponent<Counter>();
+
+      cut.Find("button").Click();
+
+      cut.Find("p").MarkupMatches("<p>Current count: 1</p>");
+    }
+  }
+}
+#endif

docs/samples/tests/xunit/FooBarComponentFactory.cs

@@ -1,3 +1,4 @@
+#if NET5_0_OR_GREATER
 namespace Bunit.Docs.Samples
 {
     using System;
@@ -12,4 +13,5 @@ public bool CanCreate(Type componentType)
         public IComponent Create(Type componentType)
             => new Bar();
     }
-}
+}
+#endif

docs/site/docfx.json

@@ -6,7 +6,6 @@
           "files": [
             "bunit.core/bunit.core.csproj",
             "bunit.web/bunit.web.csproj",
-            "bunit.web.testcomponents/bunit.web.testcomponents.csproj"
           ],
           "exclude": [ "**/bin/**", "**/obj/**" ],
           "src": "../../src"

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

@@ -72,7 +72,7 @@ With that in place, lets look at a simple example that tests the following `<Hel
 The test above does the following:
 
 1. Creates a new instance of the disposable bUnit <xref:Bunit.TestContext>, and assigns it to `ctx` the variable using the `using var` syntax to avoid unnecessary source code indention.
-2. Renders the `<HelloWorld>` component using <xref:Bunit.TestContext>, which is done through the <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> method. We cover passing parameters to components on the <xref:passing-parameters-to-components> page.
+2. Renders the `<HelloWorld>` component using <xref:Bunit.TestContext>, which is done through the `Render(RenderFragment)` method. We cover passing parameters to components on the <xref:passing-parameters-to-components> page.
 3. Verifies the rendered markup from the `<HelloWorld>` component using the `MarkupMatches` method. The `MarkupMatches` method performs a semantic comparison of the expected markup with the rendered markup.
 
 > [!TIP]
@@ -119,7 +119,7 @@ We can remove some boilerplate code from each test by making the <xref:Bunit.Tes
 
 [!code-cshtml[HelloWorldImplicitContextRazorTest.razor](../../../samples/tests/xunit/HelloWorldImplicitContextRazorTest.razor)]
 
-Since xUnit instantiates test classes for each execution of the test methods inside them, and disposes of them after each test method has run, we simply inherit from <xref:Bunit.TestContext>, and methods like <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> can then be called directly from each test. This is seen in the listing above. 
+Since xUnit instantiates test classes for each execution of the test methods inside them, and disposes of them after each test method has run, we simply inherit from <xref:Bunit.TestContext>, and methods like <xref:Bunit.TestContext.Render(RenderFragment)> can then be called directly from each test. This is seen in the listing above. 
 
 # [NUnit](#tab/nunit)
 
@@ -129,7 +129,7 @@ Since xUnit instantiates test classes for each execution of the test methods ins
 
 Since NUnit instantiates a test class only once for all tests inside it, we cannot simply inherit directly from <xref:Bunit.TestContext> as we want a fresh instance of <xref:Bunit.TestContext> for each test. Instead, we create a helper class, `BunitTestContext`, listed above, and use that to hook into NUnit's `[SetUp]` and `[TearDown]` methods, which runs before and after each test. The `BunitTestContext` class inherits from the <xref:Bunit.TestContextWrapper> type, which is included specifically to make this scenario easier.
 
-Then methods like <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> can be called directly from each test, as seen in the listing above.
+Then methods like <xref:Bunit.TestContext.Render(RenderFragment)> can be called directly from each test, as seen in the listing above.
 
 # [MSTest](#tab/mstest)
 
@@ -139,7 +139,7 @@ Then methods like <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components
 
 Since MSTest instantiates a test class only once for all tests inside it, we cannot simply inherit directly from <xref:Bunit.TestContext> as we want a fresh instance of <xref:Bunit.TestContext> for each test. Instead, we create a helper class, `BunitTestContext`, listed above, and use that to hook into MSTest's `[TestInitialize]` and `[TestCleanup]` methods. This runs before and after each test. The `BunitTestContext` class inherits from the <xref:Bunit.TestContextWrapper> type, which is included specifically to make this scenario easier.
 
-Then methods like <xref:Bunit.TestContext.Render(Microsoft.AspNetCore.Components.RenderFragment)> can be called directly from each test, as seen in the listing above.
+Then methods like <xref:Bunit.TestContext.Render(RenderFragment)> can be called directly from each test, as seen in the listing above.
 
 ***
 
@@ -181,7 +181,7 @@ This is a simple example of writing tests in `.cs` files which tests the followi
 The test above does the following:
 
 1. Creates a new instance of the disposable bUnit <xref:Bunit.TestContext>, and assigns it to the `ctx` variable using the `using var` syntax to avoid unnecessary source code indention.
-2. Renders the `<HelloWorld>` component using <xref:Bunit.TestContext>, which is done through the <xref:Bunit.TestContext.RenderComponent``1(System.Action{Bunit.ComponentParameterCollectionBuilder{``0}})> method. We cover passing parameters to components on the <xref:passing-parameters-to-components> page.
+2. Renders the `<HelloWorld>` component using <xref:Bunit.TestContext>, which is done through the <xref:Bunit.TestContext.RenderComponent``1(Action{Bunit.ComponentParameterCollectionBuilder{``0}})> method. We cover passing parameters to components on the <xref:passing-parameters-to-components> page.
 3. Verifies the rendered markup from the `<HelloWorld>` component using the `MarkupMatches` method. The `MarkupMatches` method performs a semantic comparison of the expected markup with the rendered markup.
 
 > [!TIP]
@@ -198,7 +198,7 @@ We can remove some boilerplate code from each test by making the <xref:Bunit.Tes
 
 [!code-csharp[HelloWorldImplicitContextTest.cs](../../../samples/tests/xunit/HelloWorldImplicitContextTest.cs)]
 
-Since xUnit instantiates test classes for each execution of the test methods inside them, and disposes of them after each test method has run, we simply inherit from <xref:Bunit.TestContext>, and methods like <xref:Bunit.TestContext.RenderComponent``1(System.Action{Bunit.ComponentParameterCollectionBuilder{``0}})> can then be called directly from each test. This is seen in the listing above. 
+Since xUnit instantiates test classes for each execution of the test methods inside them, and disposes of them after each test method has run, we simply inherit from <xref:Bunit.TestContext>, and methods like <xref:Bunit.TestContext.RenderComponent``1(Action{Bunit.ComponentParameterCollectionBuilder{``0}})> can then be called directly from each test. This is seen in the listing above. 
 
 # [NUnit](#tab/nunit)
 
@@ -208,7 +208,7 @@ Since xUnit instantiates test classes for each execution of the test methods ins
 
 Since NUnit instantiates a test class only once for all tests inside it, we cannot simply inherit directly from <xref:Bunit.TestContext> as we want a fresh instance of <xref:Bunit.TestContext> for each test. Instead, we create a helper class, `BunitTestContext`, listed above, and use that to hook into NUnit's `[SetUp]` and `[TearDown]` methods, which run before and after each test.
 
-Then methods like <xref:Bunit.TestContext.RenderComponent``1(System.Action{Bunit.ComponentParameterCollectionBuilder{``0}})> can be called directly from each test, as seen in the listing above.
+Then methods like <xref:Bunit.TestContext.RenderComponent``1(Action{Bunit.ComponentParameterCollectionBuilder{``0}})> can be called directly from each test, as seen in the listing above.
 
 # [MSTest](#tab/mstest)
 
@@ -218,7 +218,7 @@ Then methods like <xref:Bunit.TestContext.RenderComponent``1(System.Action{Bunit
 
 Since MSTest instantiates a test class only once for all tests inside it, we cannot simply inherit directly from <xref:Bunit.TestContext> as we want a fresh instance of <xref:Bunit.TestContext> for each test. Instead, we create a helper class, `BunitTestContext`, listed above, and use that to hook into MSTest's `[TestInitialize]` and `[TestCleanup]` methods. This runs before and after each test.
 
-Then methods like <xref:Bunit.TestContext.RenderComponent``1(System.Action{Bunit.ComponentParameterCollectionBuilder{``0}})> can be called directly from each test, as seen in the listing above.
+Then methods like <xref:Bunit.TestContext.RenderComponent``1(Action{Bunit.ComponentParameterCollectionBuilder{``0}})> can be called directly from each test, as seen in the listing above.
 
 ***
 

docs/site/docs/interaction/trigger-event-handlers.md

@@ -52,7 +52,7 @@ This is what happens in the test:
 1. In the arrange step of the test, the `<ClickMe>` component is rendered and the `<button>` element is found using the [`Find(string cssSelector)`](xref:Bunit.RenderedFragmentExtensions.Find(Bunit.IRenderedFragment,System.String)) method.
 2. The act step of the test is the `<button>`'s click event handler. In this case, the `ClickHandler` event handler method is invoked in three different ways:
    - The first and second invocations use the same [`Click`](xref:Bunit.MouseEventDispatchExtensions.Click(AngleSharp.Dom.IElement,System.Int64,System.Double,System.Double,System.Double,System.Double,System.Int64,System.Int64,System.Boolean,System.Boolean,System.Boolean,System.Boolean,System.String)) method. It has a number of optional arguments, some of which are passed in the second invocation. If any arguments are provided, they are added to an instance of the `MouseEventArgs` type, which is passed to the event handler if it has it as an argument. 
-   - The last invocation uses the [`Click`](xref:Bunit.MouseEventDispatchExtensions.Click(AngleSharp.Dom.IElement,Microsoft.AspNetCore.Components.Web.MouseEventArgs)) method. This takes an instance of the `MouseEventArgs` type, which is passed to the event handler if it has it as an argument.
+   - The last invocation uses the [`Click`](xref:Bunit.MouseEventDispatchExtensions.Click(AngleSharp.Dom.IElement,MouseEventArgs)) method. This takes an instance of the `MouseEventArgs` type, which is passed to the event handler if it has it as an argument.
 
 All the event dispatch helper methods have the same two overloads: one that takes a number of optional arguments, and one that takes one of the `EventArgs` types provided by Blazor.
 

docs/site/docs/interaction/trigger-renders.md

@@ -7,7 +7,7 @@ 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(Microsoft.AspNetCore.Components.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>). 
+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>). 
 
 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.
 

docs/site/docs/providing-input/controlling-component-instantiation.md

@@ -31,7 +31,4 @@ Then, before rendering the component under test, add the `FooBarComponentFactory
 
 ## Built-in factories
 
-bUnit comes with several built-in factories that allow shallow rendering or replacing components with test dummies and test stubs. See the following pages for details:
-
-- <xref:shallow-rendering>
-- <xref:stubbing-components>
+bUnit comes with several built-in factories that allow shallow rendering or replacing components with test dummies and test stubs. See the <xref:substituting-components> page for details.