Support co-located test scenarios

[benjaminsampica]

I'm building pretty small worker services or web api's and am trying to avoid a ton of small test projects. However, when I use TUnit on this same project (using XML attributes in the .csproj to remove test code when going to production) I'm seeing the following warning

/src/App.Worker/obj/Debug/net9.0/TestPlatformEntryPoint.cs(10,66): warning CS7022: The entry point of the program is global code; ignoring 'TestingPlatformEntryPoint.Main(string[])' entry point.

I assume this is the root cause of it not being discovered in Rider, as well as flat out not working via running in the CLI (it instead just runs the actual application). Is it currently possible to use TUnit with tests that are co-located in the same project as production code?

[thomhurst]

You'd have to control the entry point to your application somehow.

But if you want control over starting the tests, this code should do it:

var builder = await TestApplication.CreateBuilderAsync(args);
builder.AddTUnit();
using (var app = await builder.BuildAsync())
{
    return await app.RunAsync();
}

[benjaminsampica]

Works great, thanks!