Or better yet, use ASM to parse thebytecode of the test classes and verify that each class is referenced by a test class... that way you don't need rto worry about test class names
On 9 March 2010 14:27, Jesse Farinacci <[email protected]> wrote: > Hi Bowden, > > On Tue, Mar 9, 2010 at 8:45 AM, Bowden Salis > <[email protected]> wrote: > > > > The plugin features the ability to... > > * Define an inclusion set of classes (ie. all application and test > classes) > > * Define an exclusion set of classes that you do not consider needing > tests > > * Define test classes that are placeholder/todo tests within the test > class > > set (to classify as warnings) > > * Define a failure threshold for the Maven build (ie. error, warn or > none) > > > > It would be cool if we could use multiple naming patterns. For > example, I often have : > > src/main/java/com/acme/MyObj.java > src/test/java/com/acme/MyObjTest.java > src/it/java/com/acme/MyObjHibernateTest.java > > So, it would not be sufficient to validate existence of MyObjTest, but > I'd also want MyObjHibernate.java to exist. > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
