On Friday, July 27, 2001, at 09:31 am, Peter Donald wrote:
> On Fri, 27 Jul 2001 18:25, Stuart Roebuck wrote:
>> I was just thinking of writing a test case for LogKit when I noticed the
>> introduction of other unit tests and thought... great!
>
> ;)
>
>> But then I discovered that Avalon contains it's own Unit test framework
>> and I thought, "oh no - not another API to learn, what's wrong with
>> JUnit?
>> ".
>
> well I don't like some of design decisions in it but there is nothing
> wrong
> with junit. In fact there is many things right with junit ;)
>
>> Please tell me there's a sensible reason for all this duplication and
>> that
>> it's not because the open source community is not collaborating, or is
>> suffering from the "not invented here" syndrome!
>
> Well testlet is something I have been using forever in my own projects.
> Much
> of the code that I imported into avalon from these existing projects
> already
> had unit tests in testlet. Besides I couldn't be bothered learning another
> API ;)
>
> As soon as we need something thats in junit or it's associated
> infrastructure
> (reports from ant come to mind) then we will prolly switch. Eventually
> after
> ant2 is released I plan to go back and rehack testlet in it's mold.
> Basically
> a way to do all sorts of tests (unit/functional,black/white box etc) in
> one
> medium. However till then ... ;)
Well, if you think of moving to JUnit I'd be happy to assist (within the
limit time resource I have!). I appreciate that Testlet's API is probably
easy, but there is enough changing in IT that I *really* do appreciate the
standards, even if they are changing all the time.
We all have our pet projects and we also have those on the periphery that
are contributing tools or utilities. LogKit is an example of a peripheral
tool for me. It can't be a pet project, I don't have time, but it
provides useful functionality and I'm more than happy to contribute back
if there are facilities I want to add for my own work. But time and ease
is critical. It's very hard to justify learning new APIs of an
alternative unit testing framework just to be able to add a unit test to a
'periphery' project for the sake of completeness. Standardizing on these
building blocks could make such a difference to 'peripheral' participation
that I don't think this issue should be under-estimated.
I would really strongly encourage you to consider pushing JUnit towards
the benefits you see in Testlet rather than running a parallel project.
Unit testing is such a fundamental part of coding nowadays and the
integration of Ant and JUnit and the plethora of useful add-ons, make it a
solid basis for a standard.
Stuart.
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
