commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject Re: [lang] 3.0, what's in; what's out
Date Sun, 15 Mar 2009 02:23:50 GMT
On Sat, Mar 14, 2009 at 4:20 PM, sebb <sebbaz@gmail.com> wrote:
> On 14/03/2009, Jörg Schaible <joerg.schaible@gmx.de> wrote:
>> Gary Gregory wrote:
>>
>>  >> -----Original Message-----
>>  >> From: sebb [mailto:sebbaz@gmail.com]
>>  >> Sent: Saturday, March 14, 2009 4:52 AM
>>  >> To: Commons Developers List
>>  >> Subject: Re: [lang] 3.0, what's in; what's out
>>  >> >
>>
>> >> >  And the various other backwards incompatible changes that people
have
>>  >> >  been requesting.
>>  >>
>>  >> Removal of AllxxxTest classes that just group other tests.
>>  >> These just tend to get out of date, potentially complicate the POM,
>>  >> and IMO don't offer much added value.
>>  >
>>  > -1
>>  >
>>  > I use package-level test suites all the time from Eclipse. Running all
>>  > tests in a given package is a very reasonable thing to do IMO. Otherwise I
>>  > am forced to the command line where I often cannot ask Ant or Maven to
>>  > even run tests in a given package. I am stuck with whatever the build's
>>  > test target does. Not only that but I'd have to sit through a build every
>>  > time...
>>
>>
>> Especially with Eclipse there's no need. Open the context menu of the
>>  package and select run as unit test (or the project to run all tests at
>>  once). For me those AllXxxxTest suites are simply annoying.
>>
>
> And it's very easy to miss out a test - I've just found out that
> ShortPrefixToStringStyleTest is not in the BuilderTestSuite.
>
> As it happens, one of its tests fails, so when I used Eclipse to run
> everything (at least twice, because of the suites - yuk!) I found the
> missing test class.
>
> There may be other missing tests - who knows? - and it's quite tedious
> finding out.

Two separate issues.

1/ Do we hook the build to the tests or the suites. I've updated the
pom.xml to point to *Test rather than to talk to the suites. I'd
delete the build.xml, but I suspect people would complain. So any
*Test should be hooked up now and ongoing.

2/ Do we keep the suites around for some kind of value. Given that all
the tests take 23 seconds on my not new laptop, I'm not seeing a great
need to have to keep remembering to add a Test to the Suite.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message