Best way to run a class with two different DI injection types

[rodrigovaras]

Hello,
I have a test class that has a main contract interface that is used by most of the test methods. I have 2 different implementations of that interface and I would like to test the same test class with 2 different DI injections. Right now I have to subclass the test class and manually pass the interface implementation to the base class. Result, 3 C# .cs files, would like to reduce to 1 where i can inject multiple combinations to the constructor.
Maybe there is already a way to achieve this and I'm missing it.
Would like something like this:
[MyDependencyInjectionDataSource()]
[MyDependencyInjectionDataSource()]
public class MyTest(IContract contract)
{
...
}

[thomhurst]

This is how the existing DI data source attribute looks: https://github.com/thomhurst/TUnit/blob/27a978e1a1355e09c16d0cb3b345bafbd4a8cd04/TUnit.Core/Attributes/TestData/DependencyInjectionDataSourceSourceAttribute.cs

You'd basically need to adjust it to return two rows of object[] instead of just 1.

[rodrigovaras]

[rodrigovaras]

It seems to work but now its hard to see what test belong to each of the desired data source. Adding some sort of label for each and generate a test class with a better name would be even better to make the experience better

[thomhurst]

https://tunit.dev/docs/customization-extensibility/argument-formatters/

[thomhurst]

Alternatively: https://tunit.dev/docs/test-authoring/test-data-row/#available-properties

[metacoder-feff]

@rodrigovaras
Very interesting feature of TUnit is:

// Arguments can also be applied at the class level to parameterize the constructor
[Arguments(10)]
[Arguments(100)]
public class ClassLevelArgumentTests(int divisor)
{
//...
}

The result looks like:

You can parameterize your class by string value and build IContract at setup stage.