The only way you could test for that type of circumstance... one where something may happen... is to do so with a timeout. In other words, you cannot let the test pass simply because the first event occurred.
Two ways to handle this... with sequences:
Instead, you write a test that expects 2 clicks. In the assertion handler (which would only be reached if both clicks occur) you would fail the test:
fail('i shouldnt be here');
In the Waiter for the 2nd click, you would specify a timeout handler. That timeout handler will get called in the 2nd click does not occur in the specified time... (finding that time is the hard part). The default timeout handler fails the test, however, in your case, your timeout handler would just happily do any assertions needed and move on. A timeout does not necessarily mean failure... in your case, it is correct
Second choice:
You could create a timer. Create an event handler for the button click which increments a counter. Start the timer, do your test. However, have your test pending on the timer's completion rather than something like the click.. In that case, you would then be able to just check the count:
private var clickCount:int = 0;
[Test]
public function testButtonClick():void {
var timer:Timer = new Timer( 100, 1 );
Async.handleEvent( this, timer, TimerEvent.COMPLETE, checkClickCount );
view.addCommentBtn.addEventListener( 'click', function( e:Event ):void { clickCount++ } );
view.addCommentBtn.dispatchEvent( new MouseEvent( 'click;, true, false ) );
}
private function checkClickCount( e:Event ):void {
assertEquals( 1, clickCount );
}
However, I can't imagine how the test you are describing could ever yield more than one click event... I am guessing the problem is elsewhere, but this will help you verify
Mike
