RE: [geclipse-dev] JUnit Tests (Clover)

["Ken Meacham" <kem@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Hi all,

I would suggest that you look into using Clover, see:
http://www.atlassian.com/software/clover/

This actually shows you which classes and in fact which lines of which
classes get tested!

We've used this at IT Innovation, integrated with our build system, and
I see that there is also Clover plugin for Eclipse :)

Regards,

Ken.
 

> -----Original Message-----
> From: geclipse-dev-bounces@xxxxxxxxxxx 
> [mailto:geclipse-dev-bounces@xxxxxxxxxxx] On Behalf Of Harald 
> Kornmayer
> Sent: 14 May 2008 09:25
> To: 'Developer mailing list'
> Subject: RE: [geclipse-dev] JUnit Tests
> 
> Hi all 
> 
> I just want to highlight another interesting number beside 
> the general statement from Mathias! 
> 
> 1. We need definitely more tests and a more systematic test 
> coverage approach! 
> 
> 2. When looking on the webpage, I recognized, that the whole 
> test suite needed approx 40 sec to complete it's tests.
> (Is this correct, Ariel??)
> More than 25% of this time is used by just one test package 
> (namely eu.geclipse.globus.resources). 
> When we remind ourselves, how long a job submission to the 
> gLite resource broker always needs, I'm really surprised by 
> the small overall time of most of the tests. 
> Are we just testing the classes, that do not interact with 
> the Grid at all? 
> 
> WE NEED MORE TESTS!
> 
> Harald 
> 
> ==========================================
> Dr. Harald Kornmayer
> Senior researcher
> 
> NEC Laboratories Europe
> IT Division
> Rathausallee 10
> D-53757 Sankt Augustin
> Germany
> 
> Phone: +49 2241 92 52 57 
> Fax:   +49 2241 92 52 99
> Email: harald.kornmayer@xxxxxxxxxxxx
> 
> NEC Europe Ltd., Registered Office: NEC House,
> 1 Victoria Road, London W3 6bL,
> Registered in England 2832014
> ==========================================
> 
>  
> 
> >>-----Original Message-----
> >>From: geclipse-dev-bounces@xxxxxxxxxxx 
> >>[mailto:geclipse-dev-bounces@xxxxxxxxxxx] On Behalf Of Stuempert, 
> >>Mathias IWR
> >>Sent: Wednesday, May 14, 2008 10:00 AM
> >>To: Developer mailing list
> >>Subject: [geclipse-dev] JUnit Tests
> >>
> >>Hi All,
> >>
> >> 
> >>
> >>I just had a look at the test results and there integration 
> into the 
> >>nightly build.
> >>
> >> 
> >>
> >>First of all I would like to thank Jie for the provision of 
> the test 
> >>framework and the provision of a lot of the already existing tests!
> >>
> >> 
> >>
> >>Second I would like to thank Ariel and Markus for integrating the 
> >>tests into the nightly build, looks really good!
> >>
> >> 
> >>
> >>But of course now I also have some questions and comments :)
> >>
> >> 
> >>
> >>Ariel, you said most of the tests currently fail. Well, at the very 
> >>first page it is stated, that more than 75% of the tests were 
> >>successful, so for me it seems that most of the tests are 
> successful, 
> >>or am I misunderstanding something?
> >>
> >> 
> >>
> >>Furthermore the first page tells me that we currently have
> >>272 tests. Does that include really ALL tests (SVN, CVS, Core, PDE, 
> >>local, Grid, .)? Furthermore the bottom left frame contains 
> a bit more 
> >>than 100 test classes. Also here is that really the full list of 
> >>tests? If I remember it correctly we have something like 
> 3000+ classes 
> >>in the framework (Does that number also take into account 
> interfaces 
> >>and auto-generated code?). So if this is all correct we have a very 
> >>low test coverage.
> >>
> >> 
> >>
> >>For me the conclusion is that we really have to provide more tests 
> >>now! So every developer, please check if you are testing 
> your classes 
> >>properly! And if you find out that you do not, please add 
> appropriate 
> >>tests!
> >>
> >> 
> >>
> >>Cheers, Mathias
> >>
> >>
> 
> _______________________________________________
> geclipse-dev mailing list
> geclipse-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/geclipse-dev
>