When I try to run flexunit with the AIRCIListener I get:
BUILD FAILED
C:\...\build.xml:245: Error launching the test runner.
My Ant target looks like this:
<target name="test"
depends="clean, init"
description="Compile TestRunner.mxml as a SWF runnable by AD">
<mxmlc file="${test.src.loc}/${test.application.name}"
configname="air"
output="${test.bin.loc}/${test.artifact.name}">
<compiler.source-path path-element="${src.loc}"/>
<compiler.source-path path-element="${test.src.loc}"/>
<!-- The TestRunner needs the flexunit libraries in the build/libs folder -->
<library-path dir="${build.libs.loc}"
append="true">
<include name="*.swc"/>
</library-path>
<library-path dir="${libs.loc}"
append="true">
<include name="*.swc"/>
</library-path>
<!-- Sets java.awt.headless=true so font compilation works in headless environments -->
<compiler.verbose-stacktraces>true</compiler.verbose-stacktraces>
<compiler.headless-server>true</compiler.headless-server>
</mxmlc>
<!-- Execute TestRunner.swf as FlexUnit tests and publish reports -->
<flexunit player="air"
swf="${test.bin.loc}/${test.artifact.name}"
toDir="${report.loc}"
haltonfailure="false"
verbose="true"/>
<!-- Generate readable JUnit-style reports -->
<junitreport todir="${report.loc}">
<fileset dir="${report.loc}">
<include name="TEST-*.xml"/>
</fileset>
<report format="frames"
todir="${report.loc}/html"/>
</junitreport>
</target>
I am using RC2 downloaded here: http://github.com/flexunit/flexunit/downloads
When I try flexUnitTasks-4.1.0.jar which I got by checking out the sources from github I get:
BUILD FAILED
C:\...\build.xml:245: java.util.concurrent.ExecutionException: command [<testcase classname='com.myproject.desktop.model::DesktopModelTest' name='testSetServerUrl' time='0.000' status='success'/>] not understood
I guess this is because the SWCs are RC2 and the jar is RC1.
When I try the RC1 SWCs with the RC1 flexUnitTasks.jar my runner hangs while executing async tests.
So none of the combinations worked for me. I got the RC1 running for a while but when I addded more tests I got this hanger which is not caused by failures in my tests because they run fine under Mac.
Any idea on this?
Thanks,
Sönke