"timfox" wrote : "jmesnil" wrote : | | There is also the alternative to put the different types of test related to a single "component" under the same tree. | | | | e.g. for remoting; all tests related to remoting would be under org.jboss.messaging.test.remoting: | | - org.jboss.messaging.test.remoting.unit | | - org.jboss.messaging.test.remoting.integration | | - org.jboss.messaging.test.remoting.timing | | - ... | | | | | | | So, "remoting" in your above example should be "core.remoting" surely? So we mirror the exact package names? yes. I started doing that when I developed Eclipse applications using their naming conventions: [url=http://wiki.eclipse.org/index.php/Naming_Conventions] The idea is that a developer most of the time is only interested by a specific piece of code and want to focus on it. E.g. if I had to add a feature to the new persistence manager and I want to run the tests to make sure I do not break it, I find it simpler to run all tests under org.jboss.messaging.core.pm.test (or something else) than to have to navigate to all the subfolders of unit, fake, integration, etc. to check which ones have tests related to the persistence manager. Of course, Hudson will still be configured to run all unit tests together, as well as integration tests et al. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111629#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...