I wanted to see if there was a known issue with FlexUnit4.1 RC2 when running AIR based tests with the "air" player option.
What I am seeing is that adl.exe launches a window, and the display says it is running tests, but no tests are ever executed. The window stays open forever until I kill it manually. The interesting thing is that I can run adl.exe from the command line using the same arguments FlexUnit says it is using, and the runner window will appear and the tests will run. I cannot imagine what the difference is between the Ant task running adl.exe and my running it from the command line.
Here is the setup.
Here is the log output:
[flexunit] Validating task attributes ...
[flexunit] Generating default values ...
[flexunit] Using default working dir [C:\EclipseWorkspace3.5\report.renderer_tests_2\Source\Flex]
[flexunit] Using the following settings for the test run:
[flexunit] FLEX_HOME: [C:\Flex\FlexSDK4.1]
[flexunit] haltonfailure: [false]
[flexunit] headless: [false]
[flexunit] display: 
[flexunit] localTrusted: [true]
[flexunit] player: [air]
[flexunit] port: 
[flexunit] swf: [C:\EclipseWorkspace3.5\report.renderer_tests_2\build\report.renderer.tests.unit.swf]
[flexunit] timeout: [1800000ms]
[flexunit] toDir: [C:\EclipseWorkspace3.5\report.renderer_tests_2\reports\xml]
[flexunit] Setting up server process ...
[flexunit] Starting server ...
[flexunit] Opening server socket on port .
[flexunit] Waiting for client connection ...
[flexunit] Found AIR version: 2.0
[flexunit] Created application descriptor at [C:\EclipseWorkspace3.5\report.renderer_tests_2\build\flexUnitDescriptor.xml]
[flexunit] Executing 'C:\DJTE\config\Flex\FlexSDK4.1\bin\adl.exe' with arguments:
[flexunit] The ' characters around the executable and arguments are
[flexunit] not part of the command.
[flexunit] Client connected.
[flexunit] Setting inbound buffer size to  bytes.
[flexunit] Receiving data ...
[flexunit] Sending acknowledgement to player to start sending test data ...
At this point, adl.exe launches but no tests run, and I have to kill the window.
Thanks in advance...
Can you post the contents of the file you are using as your runner? I'd like to verify that all the items are in place.
Are you referring to the MXML TestRunner file, or to the flexUnitDescriptor.xml file?
BTW, we are having some IT issues and all the Flex builds are broken, so it may be Monday before I can try out the RC3 FlexUnit binaries.
I am sorry, but today I can no longer reproduce this issue. I have used both 4.1RC2 and 4.1RC3 and both of them launch an adl.exe (AIR 2.0.2) that executes my tests. Perhaps my SWCs were corrupted and got fixed by the nightly builds? Anyway, sorry for the noise. Thanks for the offer of help.