Merge branch 'stable'

Author: bUnitBot

CHANGELOG.md

@@ -6,6 +6,8 @@ All notable changes to **bUnit** will be documented in this file. The project ad
 
 ## [Unreleased]
 
+## [1.29.5] - 2024-07-05
+
 ### Fixed
 
 - CI build changes to force running verification on x64 based AMD CPUs.
@@ -521,32 +523,32 @@ List of now removed features.
   1. Add the following packages to your test project: `Serilog`, `Serilog.Extensions.Logging`, and `Serilog.Sinks.XUnit`.
   2. Add the following class/extension method to your test project (which replicates the signature of the removed `AddXunitLogger` method):
 
-         ```csharp
-         using Microsoft.Extensions.DependencyInjection;
-         using Microsoft.Extensions.Logging;
-         using Serilog;
-         using Serilog.Events;
-         using Xunit.Abstractions;
-
-         namespace Bunit
-         {
-         	public static class ServiceCollectionLoggingExtensions
-         	{
-         		public static IServiceCollection AddXunitLogger(this IServiceCollection services, ITestOutputHelper outputHelper)
-         		{
-         			var serilogLogger = new LoggerConfiguration()
-         				.MinimumLevel.Verbose()
-         				.WriteTo.TestOutput(outputHelper, LogEventLevel.Verbose)
-         				.CreateLogger();
-
-         			services.AddSingleton<ILoggerFactory>(new LoggerFactory().AddSerilog(serilogLogger, dispose: true));
-         			services.AddSingleton(typeof(ILogger<>), typeof(Logger<>));
-
-         			return services;
-         		}
-         	}
-         }
-         ```
+     ```csharp
+     using Microsoft.Extensions.DependencyInjection;
+     using Microsoft.Extensions.Logging;
+     using Serilog;
+     using Serilog.Events;
+     using Xunit.Abstractions;
+
+     namespace Bunit
+     {
+     	public static class ServiceCollectionLoggingExtensions
+     	{
+     		public static IServiceCollection AddXunitLogger(this IServiceCollection services, ITestOutputHelper outputHelper)
+     		{
+     			var serilogLogger = new LoggerConfiguration()
+     				.MinimumLevel.Verbose()
+     				.WriteTo.TestOutput(outputHelper, LogEventLevel.Verbose)
+     				.CreateLogger();
+
+     			services.AddSingleton<ILoggerFactory>(new LoggerFactory().AddSerilog(serilogLogger, dispose: true));
+     			services.AddSingleton(typeof(ILogger<>), typeof(Logger<>));
+
+     			return services;
+     		}
+     	}
+     }
+     ```
 
 - The `bunit.xunit` package has been removed, since it is no longer needed (there is no code left in it).
 
@@ -1374,7 +1376,8 @@ The latest version of the library is availble on NuGet:
 - **Wrong casing on keyboard event dispatch helpers.**
           The helper methods for the keyboard events was not probably cased, so that has been updated. E.g. from `Keypress(...)` to `KeyPress(...)`.
 
-[unreleased]: https://github.com/bUnit-dev/bUnit/compare/v1.28.9...HEAD
+[unreleased]: https://github.com/bUnit-dev/bUnit/compare/v1.29.5...HEAD
+[1.29.5]: https://github.com/bUnit-dev/bUnit/compare/v1.28.9...1.29.5
 [1.28.9]: https://github.com/bUnit-dev/bUnit/compare/v1.27.17...v1.28.9
 [1.27.17]: https://github.com/bUnit-dev/bUnit/compare/v1.26.64...1.27.17
 [1.26.64]: https://github.com/bUnit-dev/bUnit/compare/v1.25.3...v1.26.64

docs/site/docs/providing-input/inject-services-into-components.md

@@ -80,6 +80,41 @@ Here is a test where the custom service provider is used via delegate:
 
 [!code-csharp[](../../../samples/tests/xunit/CustomServiceProviderFactoryUsage.cs?start=25&end=29)]
 
+## Using libraries like AutoMocker as fallback provider
+It is possible to use libraries that automatically create mock services as fallback service providers. Here is an example implementation that utilizes the AutoMocker
+
+```csharp
+public class MockServiceProvider : IServiceProvider
+{
+    private readonly AutoMocker _autoMocker = new AutoMocker();
+
+    public object? GetService(Type serviceType)
+    {
+        return _autoMocker.Get(serviceType);
+    }
+}
+```
+
+> [!WARNING]
+> An exception has to be made for `IComponentActivator`, if "Loose" mode is used. Otherwise, runtime exception can be thrown.
+
+```csharp
+public class MockServiceProvider : IServiceProvider
+{
+    private readonly AutoMocker _autoMocker = new AutoMocker(MockBehavior.Loose);
+
+    public object? GetService(Type serviceType)
+    {
+        if (serviceType == typeof(IComponentActivator))
+        {
+            return null;
+        }
+
+        return _autoMocker.Get(serviceType);
+    }
+}
+```
+
 ## Further reading
 
 A closely related topic is mocking. To learn more about mocking in bUnit, go to the <xref:test-doubles> page.

docs/site/docs/test-doubles/emulating-ijsruntime.md

@@ -88,6 +88,13 @@ var moduleInterop = JSInterop.SetupModule("hello.js");
 moduleInterop.SetupVoid("world");
 ```
 
+When testing methods that return an `IJSObjectReference`, such as `await JsRuntime.InvokeAsync<IJSObjectReference>("SomeModule.GetInstance")`, the same process can be used with the identifier associated with the interoperation, configuring the `IJSObjectReference` in the same manner as a module.
+
+```csharp
+var objectReference = JSInterop.SetupModule(matcher => matcher.Identifier == "SomeModule.GetInstance");
+objectReference.SetupVoid("world");
+```
+
 ### Module Interop Mode
 
 By default, a module Interop inherits the `Mode` setting from the root JSInterop in bUnit. However, you can override it explicitly and have it in a different mode from another module's Interop or the root JSInterop. Just set the `Mode` property, e.g.: