Note that there are some explanatory texts on larger screens.

plurals
  1. POAnt build target is failing after first junit task
    text
    copied!<p>I have an Ant build target that performs some testing using jUnit4</p> <pre><code> &lt;target name="integrationtest" depends="init, buildtests, deploytests"&gt; &lt;junit haltonfailure="false"&gt; &lt;sysproperty key="driver" value="org.openqa.selenium.firefox.FirefoxDriver" /&gt; &lt;sysproperty key="screenshotDir" value="${screenshotsDir}" /&gt; &lt;classpath&gt; &lt;pathelement location="${interfaceTestJar}"/&gt; &lt;/classpath&gt; &lt;batchtest&gt; &lt;fileset dir="${interfaceTestClasses}"&gt; &lt;include name="**/tests/Test*.class" /&gt; &lt;/fileset&gt; &lt;/batchtest&gt; &lt;/junit&gt; &lt;junit haltonfailure="false"&gt; &lt;sysproperty key="driver" value="org.openqa.selenium.ie.InternetExplorerDriver" /&gt; &lt;classpath&gt; &lt;pathelement location="${interfaceTestJar}"/&gt; &lt;/classpath&gt; &lt;batchtest&gt; &lt;fileset dir="${interfaceTestClasses}"&gt; &lt;include name="**/tests/Test*.class" /&gt; &lt;/fileset&gt; &lt;/batchtest&gt; &lt;/junit&gt; &lt;echo message="##teamcity[publishArtifacts '${artifactsDir}']" /&gt; &lt;/target&gt; </code></pre> <p>First junit task is always started, but if there is any failed tests in it, the second one isn't starts (exepected to start in any case, even if first one has failed tests)</p> <p><strong>EDIT</strong>: Seems like there is another problem. Second jUnit is not started in any case (if first is succeed or failed). In my TeamCity build log i see the following lines</p> <pre><code>[integrationtest] junit [20:06:14]: [junit] ru.company.tests.TestDateField [20:06:30]: [junit] Process exited with code 255 </code></pre> <p><code>TestDateField</code> is my first test suite. After it there are some more suites and they all succeed (and the first one too).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload