I assume it was because flexunit 4.2 needed a different version of Flex to compile against. I'll let it pass because Chris is planning to release FlexUnit 4.3 soon, when we'll be able to also update the test runner.
On 23 March 2015 at 13:23, Mihai Chira <mihai.ch...@gmail.com> wrote: > Ok, made a bit more progress on this, and figured out that our > flexunit ant task uses > flex-flexunit\FlexUnit4AntTasks\test\sandbox\libs\flexunit-core-flex-4.1.0.x-sdky.y.y.y.swc > as the flexunit library. (If this is wrong, please correct me.) > > From what I can tell, this was simply copied manually in 2010[1] from > a compilation of the FlexUnit4 project. The only conclusion that I can > draw is that this was compiled with CONFIG::useFlexClasses set to > false. > > My next step was to try to compile the FlexUnit4 project and copy the > resulting swc into FlexUnit4AntTasks\test\sandbox\libs\. > > However, when I do `git checkout apache-flexunit-4.2.0` and then > `ant`, I get this compilation error: > > [compc] > C:\......\flex-flexunit\FlexUnit4AirCIListener\src\org\flexunit\listeners\closer\AirCloser.as(35): > col: 4 Error: Access of undefined property NativeApplication. > [compc] > [compc] NativeApplication.nativeApplication.exit(); > [compc] ^ > > (Note that before doing this I also did (on the sdk project) `git > checkout apache-flex-sdk-4.14.0` and `ant` and it compiled > successfully.) > > Any ideas why I might be getting the above error? > > > [1] http://s.apache.org/V27 > > On 10 March 2015 at 17:16, Mihai Chira <mihai.ch...@gmail.com> wrote: >> I had a bit of time today to check this out again. It seems that >> UIImpersonator.testDisplay is just a Sprite, which means that the test >> runner is compiled with CONFIG::useFlexClasses set to false (see >> org/fluint/uiImpersonation/VisualTestEnvironmentBuilder.as). >> >> Does someone know how we can recompile the test runner with >> CONFIG::useFlexClasses set to true? >> >> On 22 January 2015 at 11:58, Mihai Chira <mihai.ch...@gmail.com> wrote: >>> Thanks for the ideas. >>> >>> verbose was already true. >>> if I set haltonfailure to true, it won't even produce a report for a >>> test that throws an error. >>> >>> I just realised it: I didn't have flash player debugger for IE (only >>> for the other browsers), which was the browser it launched the tests >>> in. Now that I installed it I get the full stack trace, yaay. >>> >>> But, to make progress on the actual problem of the unit test, does >>> anyone know how to show some traces in the reports? I tried this, and >>> nothing happens: >>> >>> var _logger:ILogger = Log.getLogger("FLEX_34625"); >>> Log.addTarget(new TraceTarget()); >>> _logger.error("yoyo"); >>> trace("heya"); >>> >>> On 21 January 2015 at 21:54, piotrz <piotrzarzyck...@gmail.com> wrote: >>>> Mihai, >>>> >>>> I think you have to set haltonfailure=true or verbose=true in your ant >>>> flexunit target. The you will get full report. >>>> >>>> Piotr >>>> >>>> >>>> >>>> ----- >>>> Apache Flex PMC >>>> piotrzarzyck...@gmail.com >>>> -- >>>> View this message in context: >>>> http://apache-flex-development.2333347.n4.nabble.com/Re-2-3-git-commit-flex-sdk-refs-heads-develop-FLEX-34625-CAUSE-When-focusThickness-is-set-to-0-the-B-tp44185p44486.html >>>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
