Comments on: Adventures in NUnit test categorization

By: Greg Finzer

Greg Finzer — Fri, 28 Sep 2007 16:17:06 +0000

Thanks Andy, any feedback is appreciated. The next version of the NUnit Test Generator will have the ability to create min/max/null testing.

By: Andy

Andy — Thu, 27 Sep 2007 15:09:30 +0000

Thanks, Greg! This generator is slick.

By: Greg Finzer

Greg Finzer — Thu, 27 Sep 2007 12:25:26 +0000

This is a great article. Categories are especially useful when your code base matches more closely with the database model than the domain model. Our current project is like this since we have generated most of our code and we are using a table-class to interact with NHibernate. We are using a tool to generate our NUnit tests as well.

http://www.kellermansoftware.com/p-30-nunit-test-generator.aspx

By: Test Early » Out of the box test categorization in JUnit 4

Test Early » Out of the box test categorization in JUnit 4 — Wed, 10 Jan 2007 05:38:25 +0000

[...] The newest version of JUnit does not contain a category annotation, like its rival TestNG or its distant cousin NUnit; however, this doesn’t mean you can’t easily categorize your tests. Much like pre-JUnit 4, the solution involves the use of suites; however, as anyone who is actually using JUnit 4 knows, suites, as we used to them, are history– they’ve been replaced with annotations. [...]

By: Jonathan Cogley

Jonathan Cogley — Sun, 11 Jun 2006 16:13:17 +0000

Andy,

Great post!

This is exactly what we use! We use the Category attribute to differentiate between database read and DatabaseWrite tests (as DatabaseWrite tests are much more costly since the database needs to be reset) - we also mark Mock tests since they run much more quickly. This gives us a quick way to separate tests based on their execution speed without splitting up their logical organization - for example, having the tests for Authentication split across multiple unit test projects makes it difficult to navigate when adding new features.