In the interest of limiting the change necessary, let me suggest the following complete naming scheme:
First I think the standard naming convention is: - *TestCase for abstract superclasses of tests, not for test classes themselves - *Test for tests (Many of the matrix tests and all clustering tests are named Test* now. If it's just those... may be worth the effort to standardize IMHO. Even if it's purely naming convention stuff.) So most tests follow that. Then we could add: - *IntegrationTest for long-running tests, or - *.integration.*Test as a convention, for putting these in their own package I am indifferent between these two. On Fri, Sep 18, 2009 at 11:33 AM, Isabel Drost <isa...@apache.org> wrote: > One way would be to agree on a common naming schema (something like > "any test class <name_of_class>ITest" should go into the integration > suite and "any test class <name_of_class>UTest" should go into the unit > test suite. > > Then in the surefire plugin you can define separate includes/ excludes > based on pattern matching on these names for execution phases utest and > integration-test.
