strange problem with junit and and

[Sascha Ernst]

Hello,

First some words about my environment:
Win XP, java 1.6, ant 1.7.1

I have a problem with the combination of ant and junit.
From my point of view they are not related to the well known and documented classloader issues
(even if the error message leads to that direction)....


Here ist my junit task:

  <target name="run.junit.tests"
          depends="init"
          unless="release"
                                 if="junit" >

                <mkdir dir="${temp.dir}/junit"/>

                <junit printsummary="withOutAndErr"
                       haltonfailure="false"
                       haltonerror="false"
                       showoutput="true"
                       timeout="60000"
                       tempdir="${temp.dir}" >
                  <classpath refid="irma.build.classpath" />

      <formatter type="xml"/>

      <batchtest fork="yes" todir="${temp.dir}/junit">
        <fileset dir="${base.src.dir}">
          <include name="**/test/*.java"/>
        </fileset>
        <fileset dir="${irma.src.dir}">
          <include name="**/test/*.java"/>
        </fileset>
      </batchtest>

    </junit>

When I start the junit tasks it begins to run tests. After some time it stops with this error message.

    [junit] Test com.xtramind.common.http.test.TestService FAILED
    [junit] Test com.xtramind.common.http.test.TestServlet FAILED
BUILD FAILED
F:\NightlyBuildSystem\NBS-run-20090609061149\developer\irma\buildfiles\irma\build.xml:3394: The following error occurred while executing this line:
F:\NightlyBuildSystem\NBS-run-20090609061149\developer\irma\buildfiles\irma\build.xml:1392: org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter is not a JUnitResultFormatter

Up to this point, a lot of junit reports in xml format have been written (using this XMLJUnitResultFormatter).

I did several tests and figured this out:
The reason for this behavior is based in the timeout setting.
If I lower the timeout, the problem occurs earlier, if I upper it, it occurs later.
If I drop the timeout completely, all tests were executed and reported.

We have some tests which take quite a lot of time and we even HAD tests which were interactive and blocking until user interaction (which never
occurred in  our nightlybuildsystem). These test were the reason to set the timeout.

Do you have any ideas why a fireing timeout causes such an error)?
And how can I prevent this ?

Ein Gruss von der Saar

--
Sascha Ernst
Dipl. Inform.
Head of Software Quality Management
________________________________

Telefon: + 49 (0)681 - 302 - 5133
Telefax: + 49 (0)681 - 302 - 5109
E-Mail: sascha.ernst@...<mailto:sascha.ernst@...>
Website: http://www.living-e.com
________________________________

Living-e AG
Campus D3 2
66123 Saarbrücken
________________________________

Vorstand: Guido Polko
Aufsichtsratsvorsitzender: Uwe Feuersenger
Amtsgericht: Mannheim, HRB 111323