IHostApplicationBuilder support

[mikeholczer]

We have a bunch of extension methods on IHostApplicationBuilder for writing up Dependency Injection and IConfiguration providers that are used in our application. I'd like to be able to reuse those extensions methods for setting up CI and Config for running integration tests with TUnit, but I'm not sure what the cleanest way to do that would be. In the Microsoft.Extensions.Logging Integration section there is an example of using a IHostBuilder (and it looks like I could use the more modern IHostApplicationBuilder in it's place), but it's not clear to me where that code would actually go.

Is the idea that one would create an IHostBuilder or IHostApplicationBuilder inside a test method? or maybe in the constructor of a ClassDataSource?

[mikeholczer]

I've taken the fixture class that I have been using with XUnitv3, and now have it set as a PerTestSession ClassDataSource in my test class. That seems to be working well, but then I can't use the AddTUnit or AddTUnitLogging methods to set it's logging to be "sent' to TUnit because TestContext.Current is null when that's being executed.

[thomhurst]

In your started can you call AddCorrelatedTUnitLogging ?

This should fallback to baggage per-request scope

Edit: oh wait that's asp.net specific so won't work for you.

Edit 2: maybe I can make this work purely off of activities so it doesn't need any asp.net dependencies

[mikeholczer]

Ok, I meant let the TestContext be resolved when TUnitLogger.Log is called.

I think I figured out why the loggingBuilder.AddConsole(); line isn't working. Looks like Microsoft's ConsoleLoggerProcessor ends up queing messages as they come in and then processes the queue on a separate thread. I'm going try creating a version that doesn't do that.

[mikeholczer]

My hacked together logging provider that calls Console.WriteLine on the synchronously does work, so if you're idea doesn't pan out, a proper version of that is an option I could take.

[mikeholczer]

@thomhurst saw that you moved CorrelatedTUnitLogger to TUnit.Logging.Microsoft in #5532. I've been able test that with the latest release and it's solving this need. Thank you.