You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With NUnit 2.5, the [TestFixture] attribute is optional--the existence of a [Test] or [TestCase] is enough. It would be nice to have an analyzer option to enforce not using the attribute since it is now generally redundant.
Thank you
The text was updated successfully, but these errors were encountered:
@sdrager-emoney Thanks for your suggestion. Personally I still put the [TestFixture] on all tests. This make it clear to me. Especially in case of a derived class which itself doesn't contain any [Test] only some overrides of a base class.
Having said that, I can always disable such a rule if it existed.
Are you willing to put up PR for such a rule?
If we wanted to do this, we could possibly just mark [TestFixture] as [Obsolete] in NUnit, though doing that is less flexible than having a code analysis rule.
With NUnit 2.5, the [TestFixture] attribute is optional--the existence of a [Test] or [TestCase] is enough. It would be nice to have an analyzer option to enforce not using the attribute since it is now generally redundant.
Thank you
The text was updated successfully, but these errors were encountered: