Is it possible to change the order of parameter creation?

[Ergamon]

I am still experimenting on some way to use TUnit in conjunction with AutoFixture.

The basics now work super fine.

In the end a test is a flow through different steps. So in the brain of a test developer the test class is constructed and then the method is called. Basically this is how TUnit works, but TUnit is creating the parameters upfront, before creating the ctor paramaters. Due to the customizations order is in AutoFixture based tests very important.

In my approach there is a fixture factory in the background and the first time any component needs a fixture it is created and stored in the TestBuilderContext.

I show some code what I am trying to do:
Given 2 classes sharing a dependency:

public interface IDependency
{
}

public class Foo
{
  public Foo(IDependency dependency)
  {
    Dependency = dependency;
  }

  public IDependency Dependency { get; }
}

public class Bar
{
  public Bar(IDependency dependency)
  {
    Dependency = dependency;
  }

  public IDependency Dependency { get; }
}

Now lets write a simple test using a frozen dependency:

[ClassConstructor<AutoClassConstructor>]
public sealed class AutoTests
{
  private readonly IDependency _dependency;

  public AutoTests([Frozen] IDependency dependency)
  {
    _dependency = dependency;
  }

  [Test]
  [AutoData]
  public async Task TestFoo(Foo foo)
  {
    await Assert.That(foo.Dependency)
      .IsSameReferenceAs(_dependency);
  }

  [Test]
  [AutoData]
  public async Task TestBar(Bar bar)
  {
    await Assert.That(bar.Dependency)
      .IsSameReferenceAs(_dependency);
  }
}

Of course with the current TUnit these tests fail, cause the AutoDataAttribute is called before the AutoClassConstructor. For this to work I would need it the other way round.
Or is there some other trick to code this working?

[thomhurst]

I've raised a pr for autofixture support. Let's revisit this after