geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "cian" <>
Subject RE: Starting writing testcases
Date Thu, 13 Nov 2003 09:28:47 GMT
I figured the core module was the one to start with as well.

Okay, I'll start writing test cases from org.apache.geronimo.ejb, down. I
suggest we work our way down the clover report (I can send you a copy, if
you haven't got it to work) dealing with packages with no test cases first.
Partial test coverage being better than none at all.

-----Original Message-----
From: Jesse Beaumont []
Sent: Wednesday, November 12, 2003 9:58 PM
Subject: RE: Starting writing testcases

Hi Cian,

I've started putting together some unit tests for the core packages.  In
particular I am currently writing tests for the classes in

My intention was to move down the package list on the core module first.


-----Original Message-----
From: cian []
Sent: 12 November 2003 03:19
Subject: Starting writing testcases


I've been browsing the mail archives, and the wiki documentation, and
the best way to develop a deeper understanding this project is either to
write some test cases, or write documentation. I've run clover, and
seems to be plenty of the code that needs unit testing. However, I'd
not repeat what other people are doing.


1) Are other people writing unit tests. If so what?
2) Are there particular components that need testing more badly than
(for example: core, common, or kernel).
3) How do I get a license for clover? Do I just tell them that I'm
on this project, or is there another method?

Further point. It might be worth ammending the documentation to point
that you have to add the command line option: -Dmaven.test.force=true



PS - I'll introduce myself if/when I add something to this project ;)

---  Disclaimer  ---

Unless otherwise agreed expressly in writing by a Director of Edina
Software, this communication is to be treated as confidential and the
information in it may not be used or disclosed except for the purpose for
which it has been sent. If you have reason to believe that you are not the
intended recipient of this communication, please contact the sender

View raw message