Re: Here is my Centipede scepticism

Nick Chalko wrote:
> Mats Henricson wrote:
>> My claim is that it doesn't work! I can't use your javadoc
>> cent, since it doesn't do what I want. I can't use your
>> JUnit cent (I assume there is such a thing) since it can't
>> possibly know the names of the JUnit classes I want to
>> run.
> 
> Standard practice is to name you test *Test   the junit examples show 
> running test that match that pattern.
> That is what our cent does.

Exactly what I expected, and not what I need. I run them
in a specific order, because some of them have annoying
output that I want see last. Also, it is common to turn
off some tests, so **/*Test.java does not work for me.

> Maybe it fits your needs, maybe not.  Perhaps i can be tweeked to get 
> what you want, maybe not.

Of course it can be tweaked, but the result would be
something that is more complex than the original. Here
is my current JUnit task:

   <target name="test" depends="compile"
           description="Runs UPL JUnit tests">
     <junit fork="yes" printsummary="off" newenvironment="true">
       <classpath refid="compile.classpath"/>
       <formatter type="brief" usefile="false"/>
       <test name="info.codeq.upl.test.TranslatorTest"/>
       <test name="info.codeq.upl.test.SerializationTest"/>
       <test name="info.codeq.upl.test.RegionTest"/>
       <test name="info.codeq.upl.test.JaxmTest"/>
       <test name="info.codeq.upl.test.PrefsTest"/>
       <test name="info.codeq.upl.test.UtilTest"/>
       <test name="info.codeq.upl.test.WebTest"/>
       <test name="info.codeq.upl.test.LoadWebTest"/>
       <test name="info.codeq.upl.test.HibernateTest"/>
     </junit>
   </target>

Complex? Not at all! Specific to me? Indeed. Can be made
into a cent? No way.

> But believe me I am happy I have not written 
> a ant task for junit in 12 months, on the 9 different projects I am 
> involved in.  5 for pay and 4 for free.  Junit.cent does most of what I 
> need.  If I need more I add it to the cent and let everyone benifit.

Can't see the problem, again. The JUnit task is so simple!

>> Autodownload of jars sounds scary to me, but I'm sure it
>> solves real problems in real environments. 
> 
> It is scarry at first.  But so is making sure every developer on your 
> team is using the "right" version of xalan, with the "right" version of 
> X on each of the projects you work on.  Ruper (autodownload of dependent 
> jars) really helps.

Hm... but isn't that what you use a repository for?
You put the Jars in CVS, as a binary file, and someone
updates the Jar files after that person has tested that
the new version works well with the current code.

In which way is the problem of having correct versions
of Jar files different from the problem of having correct
versions of normal source files?

>> So, does this mean that Centipede is mostly useful in
>> really complex environments, but overkill for smaller
>> projects? 
> 
> 
> Simple project can also benifit.  Expecially if our "template" is close 
> to there needs. Take a look at the 
> http://www.krysalis.org/templates/krysalis-project/

Mmmm... cool.

> defined here  
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/krysalis/krysalis-template/krysalis-project/ 

Is that directory structure, with these XML files,
available as a zip-file anywhere?

Mats




-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.