A timeout isn't usually a timing problem, it is more often the test expected a step to generate an event and it didn't. If it is a mouse-click, maybe the position is slightly off so some action on the click didn't happen.
I fixed other sort tests by calling the low-level flash APIs to determine the expected result, then using that to test the Flex code. On 5/30/13 9:03 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> Look in the flashlog.txt, there should be more info about the assert >> failure. > >Looks like a timing error: >TestCase Start: DataGridTestScript$sparkDataGridTest1 >RESULT: >scriptName=spark.scripts::DataGridTestScript&id=sparkDataGridTest1&result= >fail&elapsed=4079&phase=body&started=1369972795751&extraInfo=null&msg=Disp >atchMouseClickEvent(body:step 18) Timeout waiting for selectionChange >from sparkDataGridTests.testdg >testComplete > >And a sorting order issue: >TestCase Start: SortTestScript$MXSort >RESULT: >scriptName=spark.scripts::SortTestScript&id=MXSort&result=fail&elapsed=1&p >hase=body&started=1369972800591&extraInfo=null&msg=AssertMethodValue >(method cannot be shown)(body:step 1) method returned >cote,côte,coté,côté,川 (U+5DDD),水 (U+6C34),海 (U+6D77),雨 (U+96E8), expected >cote,coté,côte,côté,川 (U+5DDD),水 (U+6C34),海 (U+6D77),雨 (U+96E8) > >> What FP version are you running? >11.2 > >Thanks, >Justin
