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 ... ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
