fix: Drop obsolete/deprecated objects

Fixes #1887

Author: linkdotnet

docs/site/docs/interaction/render-modes.md

@@ -75,7 +75,7 @@ public void StaticRendering()
 # [Razor test code](#tab/razor)
 
 ```razor
-@inherits TestContext
+@inherits BunitContext
 @code {
   [Fact]
   public void InteractiveServer()
@@ -108,7 +108,7 @@ public void StaticRendering()
 ***
 
 ## Setting the `RendererInfo` during testing
-To control the `ComponentBase.RendererInfo` property during testing, use the <xref:Bunit.BunitContext.SetRendererInfo(Microsoft.AspNetCore.Components.RendererInfo)> method on the `TestContext` class. The `SetRendererInfo` method takes an nullable `RendererInfo` object as a parameter. Passing `null` will set the `ComponentBase.RendererInfo` to `null`. 
+To control the `ComponentBase.RendererInfo` property during testing, use the <xref:Bunit.BunitContext.SetRendererInfo(Microsoft.AspNetCore.Components.RendererInfo)> method on the `BunitContext` class. The `SetRendererInfo` method takes an nullable `RendererInfo` object as a parameter. Passing `null` will set the `ComponentBase.RendererInfo` to `null`. 
 
 A component (`AssistentComponent.razor`) might check if interactivity is given to enable a button:
 
@@ -154,4 +154,4 @@ public void SimulatingInteractiveServerRendering()
 ```
 
 > [!NOTE]
-> If a component under test uses the `ComponentBase.RendererInfo` property and the `SetRendererInfo` on `TestContext` hasn't been passed in a `RendererInfo` object, the renderer will throw an exception.
+> If a component under test uses the `ComponentBase.RendererInfo` property and the `SetRendererInfo` on `BunitContext` hasn't been passed in a `RendererInfo` object, the renderer will throw an exception.

docs/site/docs/migrations/2to3.md

@@ -15,4 +15,12 @@ To migrate, update your test project's `<TargetFramework>` (or `<TargetFramework
 ```diff
 - <TargetFramework>net8.0</TargetFramework>
 + <TargetFramework>net10.0</TargetFramework>
-```
+```
+
+## Removed obsolete and deprecated APIs
+
+bUnit 3.x removes APIs that were kept around for backwards compatibility with bUnit 1.x and were marked `[Obsolete]` or scheduled for removal:
+
+- `TestContext` class: use `BunitContext` instead.
+- `RenderComponent<TComponent>()` and `RenderComponent<TComponent>(Action<ComponentParameterCollectionBuilder<TComponent>>?)`: use `Render<TComponent>()` instead.
+- `BunitSignOutSessionStateManager`: this was a test double for the obsolete `SignOutSessionStateManager` from `Microsoft.AspNetCore.Components.WebAssembly.Authentication` and has been removed. `AddAuthorization()` no longer registers it in the service collection.

src/bunit.template/template/CounterCSharpTest.cs

@@ -7,7 +7,6 @@ namespace Company.BlazorTests1;
 #if (testFramework_xunit)
 public class CounterCSharpTest : BunitContext
 #elif (testFramework_xunitv3)
-// The full qualified namespace for bUnit TestContext is used here as xunit v3 also offers a TestContext class
 public class CounterCSharpTest : BunitContext
 #elif (testFramework_nunit)
 public class CounterCSharpTest : BunitContext

src/bunit.template/template/CounterRazorTests.razor

@@ -1,7 +1,6 @@
 @*#if (testFramework_xunit) *@
 @inherits BunitContext
 @*#elif (testFramework_xunitv3)*@
-@* The full qualified namespace for bUnit TestContext is used here as xunit v3 also offers a TestContext class *@
 @inherits BunitContext
 @*#elif (testFramework_nunit)*@
 @inherits BunitContext

src/bunit/BunitContext.Obsoletes.cs

@@ -38,7 +38,7 @@ time to complete the necessary number of renders of the component under test.
 			and see if they match what is expected. If they do not,
 			consider increasing the timeout, either at the individual
 			method call level, e.g. WaitForElement("div", TimeSpan.FromSeconds(15)),
-			or via the static TestContext.DefaultWaitTimeout property.
+			or via the static BunitContext.DefaultWaitTimeout property.
 
 			Check count: {checkCount}.
 			Component render count: {componentRenderCount}.

src/bunit/Extensions/WaitForHelpers/WaitForFailedException.cs

@@ -10,11 +10,11 @@ public sealed class MissingRendererInfoException : Exception
 	/// </summary>
 	public MissingRendererInfoException()
 		: base("""
-		       A component under test is trying to access the 'RendererInfo' property, which has not been specified. Set it via TestContext.Renderer.SetRendererInfo.
+		       A component under test is trying to access the 'RendererInfo' property, which has not been specified. Set it via BunitContext.Renderer.SetRendererInfo.
 
 		       For example:
 
-		       public class SomeTestClass : TestContext
+		       public class SomeTestClass : BunitContext
 		       {
 		         [Fact]
 		         public void SomeTestCase()

src/bunit/RemovedInFutureVersionAttribute.cs

@@ -1,6 +1,5 @@
 using Bunit.TestDoubles;
 using Microsoft.AspNetCore.Components.Authorization;
-using Microsoft.AspNetCore.Components.WebAssembly.Authentication;
 
 namespace Bunit;
 
@@ -11,16 +10,9 @@ public partial class BunitContext
 	/// an authenticated user, as well as adding the <see cref="CascadingAuthenticationState"/> component to the
 	/// test contexts render tree.
 	/// </summary>
-	[RemovedInFutureVersion("SignOutSessionStateManager should be removed from the container.")]
 	public BunitAuthorizationContext AddAuthorization()
 	{
 		Services.AddCascadingAuthenticationState();
-#if !NET11_0_OR_GREATER
-		Services.AddSingleton<BunitSignOutSessionStateManager>();
-#pragma warning disable CS0618
-		Services.AddSingleton<SignOutSessionStateManager>(s => s.GetRequiredService<BunitSignOutSessionStateManager>());
-#pragma warning restore CS0618
-#endif
 		var authCtx = new BunitAuthorizationContext(Services);
 		return authCtx;
 	}