[Bug]: TUnit.AspNetCore execution order

[traiannemes]

Description

See attached example. Add breakpoints to WebApi.Program.cs -> at the beggining of the builder and after builder.Build(). Add breakpoints to to ConfigureWebHost and ConfigureTestConfiguration in base classes.

Depending on how long it takes for Postgress test container to start the breakpoints in WebApi get hit first. In my real projects (not shared here) the API starts with the wrong database connection string (basically using the local environment, not the test container one)

Not sure if it's a bug, but I would like an opinion on it.

TUnitTest.zip

on it.

Expected Behavior

Test initialization is first before API project starts.

Actual Behavior

API execution start in parallel with test initialization.

Steps to Reproduce

Set breakpoints as needed

TUnit Version

1.11.28

.NET Version

.NET 10

Operating System

Windows

IDE / Test Runner

Visual Studio

Error Output / Stack Trace

Additional Context

No response

IDE-Specific Issue?

• I've confirmed this issue occurs when running via dotnet test or dotnet run, not just in my IDE

[traiannemes]

Not related, but the reason I came to discover the first.

Should ChildTest succeed? Only Parent and SecondChild do.

public class ParentTest
{

    [ClassDataSource<InMemoryPostgres>(Shared = SharedType.PerTestSession)]
    public InMemoryPostgres Postgres { get; init; } = null!;

    [Test]
    public async Task Should_Succeed()
    {
        await Assert.That(Postgres.Container.GetConnectionString()).IsNotNull();
    }
}


public class ChildTest<T> where T : ParentTest, new()
{
    [Test]
    public async Task Should_Succeed()
    {
        T testInstance = new T();
        await Assert.That(testInstance.Postgres.Container.GetConnectionString()).IsNotNull();
    }
}

public class SecondChildTest : ParentTest
{
    [Test]
    public async Task Should_Succeed()
    {
        await Assert.That(Postgres.Container.GetConnectionString()).IsNotNull();
    }
}

[thomhurst]

Can you try v1.11.45

[traiannemes]

For generics issue I get this:

TUnit.Engine.Exceptions.TestFailedException: InvalidOperationException: Failed to expand data source for test 'Should_Succeed': Could not resolve type for generic parameter(s) of type 'ChildTest1' from constructor arguments. Type inference from method data may be required. ---> TUnit.Core.Exceptions.GenericTypeResolutionException: Could not resolve type for generic parameter(s) of type 'ChildTest1' from constructor arguments. Type inference from method data may be required.

For TUnit.AspNetCore execution order it looks the same, the API gets hit first follow by ConfigureWebHost

v1.11.45