Exception "Not a TestFixture, SetUpFixture or TestSuite, but ParameterizedFixture"

[tmx7777]

After upgrading from 3.17.0 to 4.0.0 I'm getting the following exception when running tests within the VS test runner:

Not a TestFixture, SetUpFixture or TestSuite, but ParameterizedFixture

The class looks basically like this:

[TestFixture(typeof(SomeClassA))]
[TestFixture(typeof(SomeClassB))]
[TestFixture(typeof(SomeClassC))]
internal class CommonTests<T> : TestFixtureBase
{
	// ...
}

TestFixtureBase is a base class of mine. But I doubt this could be problem.

Any help what the problem might be?
What additional information could I provide to help investigate the issue?

Thank you.

[OsirisTerje]

Can you provide a small repro for this?
It is the internal engine adapter that parses the XML from the engine that is being "surprised" by something here.
What you can do is to turn on the dump features in the runsettings file and upload the results there. That will probably give a good hint. See https://docs.nunit.org/articles/vs-test-adapter/Tips-And-Tricks.html#dumpxmltestdiscovery-and-dumpxmltestresults

[tbutler-qontigo]

That alpha works thanks (though we can't use alpha code in deployed environments). Do you have a timescale for 4.1?

[OsirisTerje]

There is one outstanding issue for 4.1, but the idea is to get it out mid-October.

[OsirisTerje]

Parametrized fixture is fixed in 4.1 and upcoming 4.2 will have the fix for generic fixtures.

[tmx7777]

Thanks for the update. Unfortunately I'm not able to use 4.0/4.1 for a whole other reason, right now. I'm using a test playlist with some filter settings and tests are executed even though they are supposed to be filtered out. I will try to isolate this with a small repro. Might take a while. Would it be okay to report this issue in the Q&A forum or what would be the proper channel (sorry for my ignorance)?

[OsirisTerje]

@tmx7777 Can you have a look at issue #941 . This looks like the same as you mention last here. There is a dev version of the adapter enclosed there. Can you verify if that one solves your issue ?