Re: [geclipse-dev] JUnit Tests

[Ariel Garcia <garcia@xxxxxxxxxx>]

Hi,

> 1. We need definitely more tests and a more systematic test coverage
> approach!

fully agree... also a test which does 
    Class myClass = new Class();
    assert.assertNotNull( myClass);
is NOT a test! ;-)

> 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??)

yes, but that is the time spent _inside_ the test code itself, which is 
essentially 0 if an exception happened soon enough (read: no proxy)

Wall clock time for running all the tests (which includes of course 
starting the eclipse environment every time) is around 4 minutes.

Cheers, Ariel