Part 3 I guess?

linkdotnet · linkdotnet · commit cf58830f5ea9 · 2023-04-03T21:04:56.000+02:00
diff --git a/docs/samples/tests/mstest/HelloWorldRazorTest.razor b/docs/samples/tests/mstest/HelloWorldRazorTest.razor
@@ -1,12 +1,10 @@
 @attribute [TestClass]
+@inherits TestContext
 @code
 {
   [TestMethod]
   public void HelloWorldComponentRendersCorrectly()
   {
-    // Arrange
-    using var ctx = new Bunit.TestContext();
-
     // Act
     var cut = Render(@<HelloWorld/>);
 
diff --git a/docs/samples/tests/mstest/HelloWorldTest.cs b/docs/samples/tests/mstest/HelloWorldTest.cs
@@ -4,14 +4,11 @@
 namespace Bunit.Docs.Samples
 {
   [TestClass]
-  public class HelloWorldTest
+  public class HelloWorldTest : TestContext
   {
     [TestMethod]
     public void HelloWorldComponentRendersCorrectly()
     {
-      // Arrange
-      using var ctx = new Bunit.TestContext();
-
       // Act
       var cut = RenderComponent<HelloWorld>();
 
diff --git a/docs/samples/tests/nunit/HelloWorldTest.cs b/docs/samples/tests/nunit/HelloWorldTest.cs
@@ -3,14 +3,11 @@
 
 namespace Bunit.Docs.Samples
 {
-  public class HelloWorldTest
+  public class HelloWorldTest : TestContext
   {
     [Test]
     public void HelloWorldComponentRendersCorrectly()
     {
-      // Arrange
-      using var ctx = new Bunit.TestContext();
-
       // Act
       var cut = RenderComponent<HelloWorld>();
 
diff --git a/docs/samples/tests/xunit/UserRightsTest.cs b/docs/samples/tests/xunit/UserRightsTest.cs
@@ -63,7 +63,6 @@ public void Test003()
     public void Test004()
     {
         // Arrange
-        using var ctx = new TestContext();
         var authContext = AddTestAuthorization();
         authContext.SetAuthorized("TEST USER");
         authContext.SetPolicies("content-editor");
@@ -82,7 +81,6 @@ public void Test004()
     public void Test0041()
     {
         // Arrange
-        using var ctx = new TestContext();
         var authContext = AddTestAuthorization();
         authContext.SetAuthorized("TEST USER");
         authContext.SetPolicies("content-editor", "approver");
@@ -101,7 +99,6 @@ public void Test0041()
     public void Test006()
     {
         // Arrange
-        using var ctx = new TestContext();
         var authContext = AddTestAuthorization();
         authContext.SetAuthorized("TEST USER");
         authContext.SetClaims(
@@ -124,7 +121,6 @@ public void Test006()
     public void Test005()
     {
         // Arrange
-        using var ctx = new TestContext();
         var authContext = AddTestAuthorization();
         authContext.SetAuthorized("TEST USER");
         authContext.SetRoles("admin", "superuser");
@@ -148,7 +144,6 @@ public void Test005()
     public void Test007()
     {
         // Arrange
-        using var ctx = new TestContext();
         var authContext = AddTestAuthorization();
         authContext.SetAuthorized("TEST USER");
         authContext.SetAuthenticationType("custom-auth-type");
diff --git a/docs/site/docs/test-doubles/emulating-ijsruntime.md b/docs/site/docs/test-doubles/emulating-ijsruntime.md
@@ -84,8 +84,6 @@ Since the .NET 5 release of Blazor, it has been possible to import JavaScript mo
 The `SetupModule` methods return a module JSInterop, which can be configured to handle JavaScript calls using the `Setup` and `SetupVoid` methods. For example, to configure bUnit's JSInterop to handle an import of the JavaScript module `hello.js`, and a call to the function `world()` in that model, do the following:
 
 ```csharp
-using var ctx = new TestContext();
-
 var moduleInterop = JSInterop.SetupModule("hello.js");
 moduleInterop.SetupVoid("world");
 ```
diff --git a/docs/site/docs/test-doubles/fake-navigation-manager.md b/docs/site/docs/test-doubles/fake-navigation-manager.md
@@ -123,7 +123,6 @@ As `<a href>` navigation is not natively supported in bUnit, the `NavigationMana
 The test utilizes the `NavigationManager` itself to achieve the same:
 
 ```csharp
-using var ctx = new TestContext();
 var navMan = Services.GetRequiredService<FakeNavigationManager>();
 var cut = RenderComponent<InterceptAHRefComponent>();
 
@@ -150,7 +149,6 @@ NavigationManager.NavigateToLogin("authentication/login", requestOptions);
 
 A test could look like this:
 ```csharp
-using var ctx = new TestContext();
 var navigationManager = Services.GetRequiredService<FakeNavigationManager>();
 
 ActionToTriggerTheNavigationManager();
diff --git a/docs/site/docs/test-doubles/faking-auth.md b/docs/site/docs/test-doubles/faking-auth.md
@@ -34,7 +34,7 @@ The following subsections demonstrate how to set the `<UserInfo>` into all three
 
 To set the state to unauthenticated and unauthorized, do the following:
 
-[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=11&end=20&highlight=3)]
+[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=11&end=19&highlight=2)]
 
 The highlighted line shows how `AddTestAuthorization()` is used to add the test-specific implementation of Blazor's authentication and authorization types to the `Services` collection, which makes the authentication state available to other services as well as components used throughout the test that require it.
 
@@ -44,23 +44,23 @@ After calling `AddTestAuthorization()`, the default authentication state is unau
 
 To set the state to authenticating and authorizing, do the following:
 
-[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=26&end=36&highlight=4)]
+[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=25&end=34&highlight=3)]
 
 After calling `AddTestAuthorization()`, the returned <xref:Bunit.TestDoubles.TestAuthorizationContext> is used to set the authenticating and authorizing state through the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetAuthorizing> method.
 
 ### Authenticated and unauthorized state
 
 To set the state to authenticated and unauthorized, do the following:
 
-[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=42&end=52&highlight=4)]
+[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=40&end=49&highlight=3)]
 
 After calling `AddTestAuthorization()`, the returned <xref:Bunit.TestDoubles.TestAuthorizationContext> is used to set the authenticated and unauthorized state through the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetAuthorized(System.String,Bunit.TestDoubles.AuthorizationState)> method.
 
 ### Authenticated and authorized state
 
 To set the state to authenticated and authorized, do the following:
 
-[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=58&end=68&highlight=4)]
+[!code-csharp[UserInfoTest.cs](../../../samples/tests/xunit/UserInfoTest.cs?start=55&end=64&highlight=3)]
 
 After calling `AddTestAuthorization()`, the returned <xref:Bunit.TestDoubles.TestAuthorizationContext> is used to set the authenticated and authorized state through the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetAuthorized(System.String,Bunit.TestDoubles.AuthorizationState)> method. 
 
@@ -78,17 +78,17 @@ The examples will use the `<UserRights>` component listed below. It uses the `<A
 
 To specify one or more roles for the authenticated and authorized user, do the following:
 
-[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=29&end=42&highlight=5)]
+[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=28&end=40&highlight=4)]
 
 The highlighted line shows how the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetRoles(System.String[])> method is used to specify a single role. To specify multiple roles, do the following:
 
-[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=48&end=62&highlight=5)]
+[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=46&end=59&highlight=4)]
 
 ### Policies
 
 To specify one or more policies for the authenticated and authorized user, do the following:
 
-[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=68&end=81&highlight=5)]
+[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=65&end=78&highlight=5)]
 
 The highlighted line shows how the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetPolicies(System.String[])> method is used to specify one policy. To specify multiple policies, do the following:
 
@@ -98,22 +98,22 @@ The highlighted line shows how the <xref:Bunit.TestDoubles.TestAuthorizationCont
 
 To specify one or more claims for the authenticated and authorized user, do the following:
 
-[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=106&end=123&highlight=5-8)]
+[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=101&end=117&highlight=4-7)]
 
 The highlighted line shows how the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetClaims(System.Security.Claims.Claim[])> method is used to pass two instances of the `Claim` type.
 
 ### Example of passing both roles, claims, and policies
 
 Let’s try to combine all the possibilities shown in the previous examples into one. The following example specifies two roles, one claim, and one policy for the authenticated and authorized user:
 
-[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=129&end=147&highlight=4-8)]
+[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=123&end=140&highlight=3-7)]
 
 With this example done, all auth-related test scenarios should be covered. If you find that one is missing, please let us know in the [bUnit discussion forum](https://github.com/egil/bUnit/discussions).
 
 ### Authentication types
 
 To specify a authentication type for the authenticated and authorized user, do the following:
 
-[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=153&end=166&highlight=5)]
+[!code-csharp[UserRightsTest.cs](../../../samples/tests/xunit/UserRightsTest.cs?start=146&end=158&highlight=4)]
 
 The highlighted line shows how the <xref:Bunit.TestDoubles.TestAuthorizationContext.SetAuthenticationType(System.String)> method is used to change the `Identity.AuthenticationType` of the user.
diff --git a/docs/site/docs/verification/async-assertion.md b/docs/site/docs/verification/async-assertion.md
@@ -26,7 +26,7 @@ Let's look at an example. Consider the following `<AsyncData>` component, which
 
 To test the `<AsyncData>` component, do the following:
 
-[!code-csharp[AsyncDataTest.cs](../../../samples/tests/xunit/AsyncDataTest.cs?start=54&end=65&highlight=3,9,12)]
+[!code-csharp[AsyncDataTest.cs](../../../samples/tests/xunit/AsyncDataTest.cs?start=52&end=62&highlight=2,8,11)]
 
 This is what happens in the test:
 
@@ -38,7 +38,7 @@ This is what happens in the test:
 
 The timeout, which defaults to one second, can be controlled by passing a `TimeSpan` as the second argument to the `WaitForAssertion()` method, e.g.:
 
-[!code-csharp[](../../../samples/tests/xunit/AsyncDataTest.cs?start=66&end=66)]
+[!code-csharp[](../../../samples/tests/xunit/AsyncDataTest.cs?start=63&end=63)]
 
 If the timeout is reached, a <xref:Bunit.Extensions.WaitForHelpers.WaitForFailedException> exception is thrown with the following error message:
 
diff --git a/docs/site/docs/verification/semantic-html-comparison.md b/docs/site/docs/verification/semantic-html-comparison.md
@@ -143,4 +143,4 @@ Let’s look at a few examples where we use the semantic comparison options list
 
 In this case, we want to verify that the markup is rendered correctly, using something such as RegEx to verify the `id` attribute (it might be generated) and ignoring the `<small>` element.  In tests we can do this like so with the `MarkupMatches()` method:
 
-[!code-csharp[SemanticHtmlTest.cs](../../../samples/tests/xunit/SemanticHtmlTest.cs#L16-L29)]
+[!code-csharp[SemanticHtmlTest.cs](../../../samples/tests/xunit/SemanticHtmlTest.cs#L16-L28)]
diff --git a/docs/site/docs/verification/verify-markup.md b/docs/site/docs/verification/verify-markup.md
@@ -30,7 +30,7 @@ To access the rendered markup of a component, just use the <xref:Bunit.IRendered
 
 To get the markup as a string, do the following:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=16&end=21&highlight=5)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=16&end=19&highlight=3)]
 
 You can perform standard string assertions against the markup string, like checking whether it contains a value or is empty.
 
@@ -70,13 +70,13 @@ In the following examples, the `<Heading>` component listed below will be used a
 
 To use the `MarkupMatches()` method to perform a semantic comparison of the output of the `<Heading>` component through its <xref:Bunit.IRenderedFragment>, do the following:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=27&end=34&highlight=5-9)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=25&end=30&highlight=3-6)]
 
 The highlighted line shows the call to the `MarkupMatches()` method. This test passes even though the insignificant whitespace is not exactly the same between the expected HTML string and the raw markup produced by the `<Heading>` component. It even works when the CSS class list is not in the same order on the `<small>` element.
 
 The `MarkupMatches()` method is also available on `INode` and `INodeList` types, for example:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=40&end=45&highlight=5-6)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=36&end=39&highlight=3-4)]
 
 Here we use the `Find(string cssSelector)` method to find the `<small>` element, and only verify it and its content and attributes.
 
@@ -85,7 +85,7 @@ Here we use the `Find(string cssSelector)` method to find the `<small>` element,
 
 Text content can also be verified with the `MarkupMatches()` method, e.g. the text inside the `<small>` element. It has the advantage over regular string comparison in that it removes insignificant whitespace in the text automatically - even between words - where a normal string `Trim()` method isn't enough. For example:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=51&end=56&highlight=5)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=45&end=48&highlight=3)]
 
 The semantic HTML comparer can be customized to make a test case even more stable and easier to maintain. For example, it is possible to ignore an element or attribute during comparison, or provide a regular expression to the comparer when comparing a specific element or attribute to make the comparer work with generated data.
 
@@ -112,11 +112,11 @@ Let's see some examples of using the [`Find(string cssSelector)`](xref:Bunit.Ren
 
 To find the `<caption>` element and the first `<td>` elements in each row, do the following:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=62&end=67&highlight=5-6)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=54&end=57&highlight=3-4)]
 
 Once you have one or more elements, you verify against them,  such as by  inspecting their properties through the DOM API. For example:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=69&end=71)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=59&end=61)]
 
 #### Auto-refreshing Find() queries
 
@@ -148,7 +148,7 @@ Let's look at a few examples  of using the assertion helpers. In the first one,
 
 Here is an example of using the <xref:Bunit.IRenderedFragment.GetChangesSinceFirstRender> method:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=77&end=90&highlight=8,11,14)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=67&end=79&highlight=7,10,13)]
 
 This is what happens in the test:
 
@@ -164,7 +164,7 @@ This example tests the `<CheckList>` component listed below. The component allow
 
 To test the end-to-end life cycle of adding and removing items from the `<CheckList>` component, do the following:
 
-[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=96&end=141)]
+[!code-csharp[](../../../samples/tests/xunit/VerifyMarkupExamples.cs?start=85&end=126)]
 
 This is what happens in the test:
 

Original file line number	Diff line number	Diff line change
`@@ -1,12 +1,10 @@`
`1`	`1`	`@attribute [TestClass]`
	`2`	`+@inherits TestContext`
`2`	`3`	`@code`
`3`	`4`	`{`
`4`	`5`	`[TestMethod]`
`5`	`6`	`public void HelloWorldComponentRendersCorrectly()`
`6`	`7`	`{`
`7`		`- // Arrange`
`8`		`- using var ctx = new Bunit.TestContext();`
`9`		`-`
`10`	`8`	`// Act`
`11`	`9`	`var cut = Render(@<HelloWorld/>);`
`12`	`10`
Original file line number	Diff line number	Diff line change
`@@ -4,14 +4,11 @@`
`4`	`4`	`namespace Bunit.Docs.Samples`
`5`	`5`	`{`
`6`	`6`	`[TestClass]`
`7`		`- public class HelloWorldTest`
	`7`	`+ public class HelloWorldTest : TestContext`
`8`	`8`	`{`
`9`	`9`	`[TestMethod]`
`10`	`10`	`public void HelloWorldComponentRendersCorrectly()`
`11`	`11`	`{`
`12`		`- // Arrange`
`13`		`- using var ctx = new Bunit.TestContext();`
`14`		`-`
`15`	`12`	`// Act`
`16`	`13`	`var cut = RenderComponent<HelloWorld>();`
`17`	`14`
Original file line number	Diff line number	Diff line change
`@@ -3,14 +3,11 @@`
`3`	`3`
`4`	`4`	`namespace Bunit.Docs.Samples`
`5`	`5`	`{`
`6`		`- public class HelloWorldTest`
	`6`	`+ public class HelloWorldTest : TestContext`
`7`	`7`	`{`
`8`	`8`	`[Test]`
`9`	`9`	`public void HelloWorldComponentRendersCorrectly()`
`10`	`10`	`{`
`11`		`- // Arrange`
`12`		`- using var ctx = new Bunit.TestContext();`
`13`		`-`
`14`	`11`	`// Act`
`15`	`12`	`var cut = RenderComponent<HelloWorld>();`
`16`	`13`
Original file line number	Diff line number	Diff line change
`@@ -143,4 +143,4 @@ Let’s look at a few examples where we use the semantic comparison options list`
`143`	`143`
`144`	`144`	In this case, we want to verify that the markup is rendered correctly, using something such as RegEx to verify the `id` attribute (it might be generated) and ignoring the `<small>` element. In tests we can do this like so with the `MarkupMatches()` method:
`145`	`145`
`146`		`-[!code-csharp[SemanticHtmlTest.cs](../../../samples/tests/xunit/SemanticHtmlTest.cs#L16-L29)]`
	`146`	`+[!code-csharp[SemanticHtmlTest.cs](../../../samples/tests/xunit/SemanticHtmlTest.cs#L16-L28)]`