Added example to home and tweaks to other pages

Author: egil

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

@@ -15,7 +15,7 @@ Rendering a component happens through bUnit's <xref:Bunit.TestContext>, and the
 
 Lets see a simple example, where we test the following `<HelloWorld>` component:
 
-[!code-cshtml[HelloWorld.razor](../../samples/components/HelloWorld.razor)]
+[!code-html[HelloWorld.razor](../../samples/components/HelloWorld.razor)]
 
 # [xUnit](#tab/xunit)
 

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

@@ -1,4 +1,4 @@
----
+---
 uid: writing-razor-tests
 title: Writing tests in Razor syntax for Blazor components
 ---
@@ -29,7 +29,7 @@ A Blazor test component is conceptually very similar to a regular test class in
 
 Besides that, Blazor test components has to inherit from  <xref:Bunit.TestComponentBase>, e.g.:
 
-[!code-html[HelloWorldTest.razor](../../samples/tests/razor/HelloWorldTest.razor#L1)]
+[!code-html[](../../samples/tests/razor/HelloWorldTest.razor#L1)]
 
 The following two sections will show how to create tests using bUnit's <xref:Bunit.Fixture> and <xref:Bunit.SnapshotTest> components.
 

docs/docs/toc.md

@@ -5,14 +5,14 @@
 ## [Fixture test options](xref:fixture-options)
 ## [SnapshotTest options](xref:snapshot-options)
 
-# [Providing input](xref:passing-parameters-to-components)
+# [Providing input](xref:providing-input)
 ## [Parameters and cascading values](xref:passing-parameters-to-components)
 ## [Inject services](xref:inject-services-into-components)
 ## [Trigger event handlers](xref:trigger-event-handlers)
 ## [Trigger renders](xref:trigger-renders)
 ## [Configure 3rd party libraries](xref:configure-3rd-party-libs)
 
-# [Verifying output](xref:verify-markup)
+# [Verifying output](xref:verifying-output)
 ## [Verify markup](xref:verify-markup)
 ## [Verify component state](xref:verify-component-state)
 ## [Semantic HTML markup comparison](xref:semantic-html-comparison)

docs/index.md

@@ -26,29 +26,22 @@ The library builds on top of existing unit testing frameworks such as xUnit, whi
 
 The library's goal is to make it easy to write _comprehensive, stable unit tests_ for Blazor Components/Razor Components. 
 
-For example, to test the [`Counter.razor`](https://github.com/egil/bunit/blob/master/sample/src/Pages/Counter.razor) component that is part of the Blazor "file-new-project" project, you can do the following, using bUnit and xUnit:
-
-```csharp
-[Fact]
-public void CounterShouldIncrementWhenClicked()
-{
-  // Arrange: render the Counter.razor component
-  var cut = RenderComponent<Counter>();
-  
-  // Act: find and click the <button> element to increment
-  // the counter in the <p> element
-  cut.Find("button").Click();
-
-  // Assert: first find the <p> element, then verify its content
-  cut.Find("p").MarkupMatches("<p>Current count: 1</p>");  
-}
-```
-
 **Go to [Documentation](xref:getting-started) to learn more.**
 
 > [!NOTE]
 > The documentation is currently being rewritten to reflect the recent changes. Please excuse the mess.
 
+### Simple example
+
+For example, to test the `<Counter>` component listed below:
+
+[!code-html[Counter.razor](./samples/components/Counter.razor)]
+
+You can do the following, using bUnit and xUnit:
+
+[!code-csharp[CounterTest.cs](./samples/tests/xunit/CounterTest.cs#L8-L20)]
+
+**Go to [Documentation](xref:getting-started) to learn more.**
 
 ### NuGet downloads
 

docs/samples/components/Counter.razor

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

docs/samples/tests/xunit/CounterTest.cs

@@ -0,0 +1,22 @@
+using Xunit;
+using Bunit;
+
+namespace Docs.Components.Xunit
+{
+    public class CounterTest : TestContext
+    {
+        [Fact]
+        public void CounterShouldIncrementWhenClicked()
+        {
+            // Arrange: render the Counter.razor component
+            var cut = RenderComponent<Counter>();
+
+            // Act: find and click the <button> element to increment
+            // the counter in the <p> element
+            cut.Find("button").Click();
+
+            // Assert: first find the <p> element, then verify its content
+            cut.Find("p").MarkupMatches("<p>Current count: 1</p>");
+        }
+    }
+}