Test methods that utilize parameters decorated with MatrixMethodAttribute and DataSourceGeneratorAttribute

[jcasale]

I have a use case where I want to use matrix tests with more than one parameter, and also provide an application (essentially a service provider that creates a fresh application and disposes it after the individual matrix test).

The MatrixMethodAttribute and DataSourceGeneratorAttribute attributes can't be combined, as I cannot decorate a method parameter with DataSourceGeneratorAttribute and decorating the method with DataSourceGeneratorAttribute prevents the use of MatrixMethodAttribute.

I notice that implementing IDisposable on the test class and building the service provider into the test class works, but it's not reusable across multiple test classes or easily merged with other test applications.

What options do I have to ensure the test methods all get a fresh application that is not reused and reliably disposed of?

[thomhurst]

I'd recommend having your application that uses your DataSourceGeneratorAttribute injected as a property in your class, or in the class constructor.

Then your method solely uses the matrix attribute

[jcasale]

Hi, it looks like DataSourceGeneratorAttribute generates data without tracking it, so it won't dispose of it after a defined lifetime.

However, looking at https://tunit.dev/docs/test-lifecycle/property-injection#nested-property-injection, it appears that ClassDataSourceAttribute does.

I set up a trivial test that implements both IAsyncInitializer and IAsyncDisposable, but only IAsyncInitializer is called.

Any idea what might cause that?

[thomhurst]

It's a current bug with the automatic tracking system that I'm trying to fix. Hopefully will be solved soon 😄

[thomhurst]

Can you try on v0.57.0?

[jcasale]

I just tried now with v0.57.1, and it's not getting called.

[thomhurst]

😢