ProceedOnEvent() timeout waiting for creationComplete

Question

Hello,
I have a test case that will not run due to proceedOnEvent not seeing the desired event.  Here's the test code:
package com.mine.components.buttonBar
          import flexunit.framework.Assert;
          import mx.collections.ArrayList;
          import mx.core.FlexGlobals;
          import mx.events.FlexEvent;
          import org.flexunit.async.Async;
          import org.fluint.uiImpersonation.UIImpersonator;
          import org.hamcrest.assertThat;
          import org.hamcrest.collection.hasItems;
          import org.hamcrest.object.equalTo;
          import org.hamcrest.object.notNullValue;
          public class ButtonBarTest
                    private var buttonBar: ButtonBar;
                    private var buttonData: Array = [{label: "one"  },{label: "two"},{label: "three"},{label: "four"},{label: "five"}];
                    [Before(async, ui)]
                    public function setUp():void
                              buttonBar = new ButtonBar();
                              buttonBar.dataProvider = new ArrayList( buttonData );
                              Async.proceedOnEvent( this, buttonBar, FlexEvent.CREATION_COMPLETE, 3000 );
                              UIImpersonator.addChild( buttonBar );
                    [After(async,ui)]
                    public function tearDown():void
                              UIImpersonator.removeChild( buttonBar );
                              buttonBar.dataProvider = null;
                              buttonBar = null;
                    [BeforeClass]
                    public static function setUpBeforeClass():void
                    [AfterClass]
                    public static function tearDownAfterClass():void
                    [Test(async, ui)]
                    public function testGet_selectedIndices():void
                              assertThat( buttonBar, notNullValue() );
                              var selectedIndices: Vector.<int> = buttonBar.selectedIndices;
                              assertThat( selectedIndices, notNullValue() );
                              assertThat( selectedIndices, equalTo( 0 ) );
                              buttonBar.selectedIndices = new Vector.<int>( 0, 2, 4 );
                              assertThat( buttonBar.selectedIndices, hasItems( 0, 2, 4 ) );
I can run the test within flashbuilder or from ant using a test runner and I get the same result.
The button bar component is derived from spark.components.SkinnableDataContainer and has its own skin.  Buttons are added to a DataGroup, one button for each dataProvider element.  The buttons and data group are added by the skin classes associated with the button bar.
I am using flexunit-4.1.0-8-4.1.016076.
I'd really appreciate some help in getting this test case to work correctly.
Thanks,
Jeff

Answer 1

In the first example, your component is added to a container attached to the system root (so a peer to the application) in the second you are attaching it directly to the application. There isnt a good reason why one should work for you and one not. However, all of the verions of Flex you mention were released after the latest release of FlexUnit so there is the chance that something changed.
I will take a look at this for you, but I can't promise when that will happen so for the moment, if the topLevelApplication trick is working, I see little wrong with that. The only thing to be aware of is that your topLevelApplication may attempt to resize, etc. based on adding a child so it might affect test time.
It may be easier to add a fixed with container (canvas or similar) to the application and then specifically target that just to mitigate the response. Another possibility, if you wish to try, you can actually pass a visualDisplayRoot to the FlexUnitCore when you instantiate it. I believe I saw you doing so in your other post.
So, you can try saying
var core:FlexUnitCore = new FlexUnitCore();
core.visualDisplayRoot = this; //assuming this is running from the main app
Some additional thoughts. If this is a Spark only project:
If flexunit is running an mx only or mx/spark environment it builds a Container for your tests. If it cannot find mx.core.Container at runtime, it builds a Group.
https://github.com/flexunit/flexunit/blob/master/FlexUnit4/src/org/fluint/uiImpersonation/ flex/FlexEnvironmentBuilder.as
Group doesnt let you call addChild. It expects you to call addElement()
Mike