buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin (JIRA)" <>
Subject [jira] Commented: (BUILDR-62) JUnit test filtering should allow custom filtering, and not test JUnit @Test annotation on class
Date Tue, 22 Apr 2008 07:33:21 GMT


Assaf Arkin commented on BUILDR-62:

I just committed this fix to SVN and also verified that the following will work:

1.  JUnit will pick any class that has one or more @Test annotated method in it.
2.  JUnit will also pick any class that has @RunWith annotation on it, or extends TestCase
(for JUnit 3.x support).
3.  When using test.include('foo') only the name 'foo' is passed to JUnit for execution, provided
that 'foo' is either #1 or #2.

> JUnit test filtering should allow custom filtering, and not test JUnit @Test annotation
on class
> ------------------------------------------------------------------------------------------------
>                 Key: BUILDR-62
>                 URL:
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.3
>            Reporter: Timo Rantalaiho
> If I understand correctly, in test_frameworks.rb
> JUnit tests are collected by taking 
> 1) everything that extends JUnit 3 TestCase
> 2) every class that is annotated with JUnit 4 @Test
> 3) every method that is annotated with JUnit 4 @Test
> 2) is clearly wrong, as @Test only applies to methods, not classes
> Also, I found no way to run JDave ( ) specs or a custom suite with
the current 1.3 trunk (22 April 2008). In 1.2, this is very easy with Buildr::Java::JUnit::JUNIT_TESTS_PATTERN
filtering by test / spec class names. 
> Some kind of an abstraction for filtering the relevant test or spec classes is important
not only for custom test framework integration, but for custom suites in big projects. Running
a lot of tests is typically faster in a suite, and when you have different sets of tests (unit,
integration, acceptance, black-box against a deployed application, ...) you typically want
to specify which set to run. For example, the continuous integration server might only run
tests against the deployed application a couple of times a day, but unit tests all the time
for fast feedback. Different grouping methods of test frameworks are framework specific, and
rather than making Buildr support framework specific ways, it could operate on an extra abstraction
> Filtering by class name has worked well elsewhere (ant, maven, buildr 1.2), so it would
be excellent if it would be included in 1.3 as well.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message