Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I cant see any difference in behaviour for class that has TestFixture attribute and not. All TearDown and SetUp are working in the same way. Is there any reason except semantics for this attribute usage?
Is purely a convenience, beginning with NUnit 2.5, if a class satisfies the conditions to be a test fixture and specifies at least a method marked with
Test,TestCaseorTestCaseSourcethan that class is treated as a test fixture.The
TestFixtureattribute is required however for parameterized or generic test fixture because in that case you also specify additional information through the attribute (parameters/concrete types).More information about the specific requirements is available at TextFixtureAttribute (NUnit 3 Documentation) and
TestFixtureAttribute (NUnit 2.0 / 2.5)