I gradually started reintegrating your original build script,
and I can confirm that it runs normally. (Should've tried that in
the first place, grmbl). So discard that previous comment.
It looks like the issue is related to your build environment. Can
you give us the specifics of your environment.
To summarize, I was able to reproduce the issue with ant +
flexUnit. And for some reason it didn't work on my pc, but it
worked on Michael Labriola's pc. But I haven't had time to
investigate this any further. The referenced thread should have my
test case as attachment.
on 25 Mar, 2013 07:24 PM
Well FYI this is my environment:
Windows 7 x64 (and Cygwin)
Java jdk1.7.0_13 64-bit
Gradle 1.4 (and the ant & groovy version which come with
FlexUnit 4.1.0-8 (latest binary version)
Now I've noticed a couple of odd things, and being new to Flex
(but not new to gradle) maybe you can shed some light:
1. Now I'm able to run the ant test target, and all but 1 test
fail, however adl.exe hangs after running the test suite (perhaps
related to the bug above)
2. Using the same FLEX_HOME and the same FLEXUNIT_LIBS (I modified
the build.xml) using gradlefx I can see in the reports dir that
some tests are generated (presence of XML report files) however
3. Is it normal that I can't see any stdout/err when running using
gradlefx? Is it possible that not capturing the ant task output is
what is preventing adl from running properly?
I would be glad to try out someone's build.gradle so that I can
see if the problem is indeed purely environment related, although
if ant works I don't see why gradlefx wouldn't. The only thing I
can think of is that gradlefx generates a TestRunner.swf and the
ant builds one based on an mxml file (CoreLibTestRunner in this
on 26 Mar, 2013 01:07 PM
Thank you Yennick!
Your little project helped me figure out what I needed to do! So I
began importing all of the .as files as well as the test .as files
into your little flexunit ANT project and after some tests ADL was
Awesome! This brings us one step further in the process of
solving this. While editing the mm.cfg file is a reasonable
temporary solution, it is not ideal when you want to share your
project with others.
I'll try this out on my pc at home tomorrow and see if it's also
solved there with the mm.cfg config.