Steven Giesel
Steven Giesel
@johanbenschop just as a headsup if you decide to do so. Normally, docs are made on the `stable` branch - this time please go from `main` and target `main` as...
We also might wanna add `xunitv3` or similar for our templates
Plus we might wanna migrate our testbase sooner or later to `v3` (probably something we only wanna do for `v2`)
> IAssertionException and ITestTimeoutException are new interfaces that we can include in bUnit and mark our assertions exceptions with. See https://xunit.net/docs/getting-started/v3/whats-new#third-party-assertion-library-extension-points We would need an abstraction and add this behavior...
We only really have two candidates, in my opinion: `ActualExpectedAssertException` and `WaitForFailedException`. The latter one is tricky - as it is used in all `WaitForXXX` operations. Now, We might want...
We added this to the docs as well as adding the exceptions. Therefore done on `v1` and more docs on `v2` for xunit.v3
Good thinking - but should we move this to v3 and align with FindByLabel? Otherwise we break our API style.
Hey @spankr Thanks for reporting this. This code is mainly for backward compatibility, and Blazor itself has roughly the same piece: ```csharp return serviceProvider.GetService() ?? new DefaultComponentActivator(serviceProvider); ``` Source: https://github.com/dotnet/aspnetcore/blob/main/src/Components/Components/src/RenderTree/Renderer.cs#L68-L69...
Indeed, that would be a fair point.
We merged the updated documentation. Thanks for reporting @spankr