Filtering JUnit integration tests based on an annotation

[David Ashman]

My team is using infinitest and we love it.  The only issue we are running into is that we have several integration tests under src/integTest/java that don't run without proper setup and are rather slow.  I'd like to filter them out, but that's not possible with the current classname filters (they are not packaged or named in any unique way).  They all do have an annotation on them that would allow me to filter.  Is there currently a way to do this?  If not, can someone point me to where the TestNG annotation filtering is happening because I can likely fork the code and add something similar for JUnit.  Optionally, is there a way in the eclipse plugin to filter out a source path altogether?

[David Gageot]

Hi David,

Sorry to here that the current filtering mechanism doesn't make it possible to filter your integration tests out.

You can't filter on annotations but if you are willing to help, one of the classes to look at is

https://github.com/infinitest/infinitest/blob/master/infinitest-lib/src/main/java/org/infinitest/filter/RegexFileFilter.java

David.

On Thu, Jun 27, 2013 at 2:41 AM, David Ashman <da...@davidashman.me> wrote:

My team is using infinitest and we love it.  The only issue we are running into is that we have several integration tests under src/integTest/java that don't run without proper setup and are rather slow.  I'd like to filter them out, but that's not possible with the current classname filters (they are not packaged or named in any unique way).  They all do have an annotation on them that would allow me to filter.  Is there currently a way to do this?  If not, can someone point me to where the TestNG annotation filtering is happening because I can likely fork the code and add something similar for JUnit.  Optionally, is there a way in the eclipse plugin to filter out a source path altogether?

--
You received this message because you are subscribed to the Google Groups "infinitest-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infinitest-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[David Ashman]

The issue is the filter interface takes the file name only.  I'd need to load the class and check the annotations and I'm concerned about the performance of that. 

Dave

You received this message because you are subscribed to a topic in the Google Groups "infinitest-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/infinitest-dev/qr4PfDnqkfs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to infinitest-de...@googlegroups.com.

[David Gageot]

Hi,

Yesterday I made some changes that might help you. Instead of a classname, TestFilter now

takes the JavaClass which is an interface on a class that is already loaded.

https://github.com/infinitest/infinitest/blob/master/infinitest-lib/src/main/java/org/infinitest/filter/TestFilter.java

David.

[David Ashman]

Excellent.  Forked and coding now.

dave

[David Ashman]

Struggling to get a new version of the plugin installed in Eclipse.  Once I build everything, how do I tell Eclipse to load the new version?  I can't seem to get it to see the update site.

dave

On June 28, 2013 at 1:19:06 AM, David Gageot (dga...@gmail.com) wrote: