well this hack is only needed for unit testing views. and unit tests for views aren't exactly pure unit tests since they rely so much on the flex framework code. I don't really know enough about the internals of Flex and why it's not enough to just add a component to an orphaned container (fluint TestEnvironment) but there are certain events that are just not fired off by Flex without having the fluint TestEnvironment added to the application object. I am sure there's a similar problem with the flexunit support and testing views but pre flexunit 4 it was very hard to test view components in the same way you can in fluint.
so, not really sure of other ways of handling it. On Sep 2, 5:23 pm, Marvin Froeder <[email protected]> wrote: > I don't know, I feel uneasy with this hacks.... > Why a unit test framework needs UI access? If that is safe why fluint code > doesn't do that? How can I know I won't break your test because you did > something different? How that will affect flexmonkey tests? > > Any idea on how to handle that on the test class? > > VELO > > On Wed, Sep 2, 2009 at 9:08 PM, eydev <[email protected]> wrote: > > > I updated the issue below with a small fix I had to do to get events > > to fire correctly in uicomponents. basically the FluintListener > > runTests() method should look like this: > > > function runTests():int { > > var testRunner:TestRunner = new TestRunner(_testMonitor); > > testRunner.testEnvironment = new TestEnvironment(); > > mx.core.Application.application.addChild > > (testRunner.testEnvironment); > > testRunner.startTests(_testSuite); > > testRunner.addEventListener(TestRunner.TESTS_COMPLETE, > > handleTestsComplete); > > return testRunner.getTestCount(); > > } > > > On Aug 27, 11:26 am, eydev <[email protected]> wrote: > > > awesome, thx! > > > > On Aug 26, 3:43 pm, velo <[email protected]> wrote: > > > > > Changes in placehttps://issues.sonatype.org/browse/FLEXMOJOS-178 > > > > > VELO > > > > > On Aug 26, 6:11 pm, Marvin Froeder <[email protected]> wrote: > > > > > > Awesome =D > > > > > But does fluint still exists? > > > > > > I thought it become part of flexunit 4 ( I can be terrible wrong > > here) > > > > > > VELO > > > > > > On Wed, Aug 26, 2009 at 5:25 PM, eugene yusim <[email protected]> > > wrote: > > > > > > Attached are the files I added/modified to get fluint support in > > > > > > flexmojos-unittest-support 3.3.0 > > > > > > > Some notes: > > > > > > > This only works with the trunk version of fluint ( > > > > > >http://fluint.googlecode.com/svn/trunk/) > > > > > > > AsVmLauncherTest,launch was failing for me when building > > flexmojos > > > > > > 3.3.0, even though I can see the swf launched 5 times. Ended up > > ignoring the > > > > > > test. > > > > > > > FUnitListener was picking up the fluint tests and then not > > running them > > > > > > causing the test app to hang, modified the listener to ignore > > fluint > > > > > > TestCase classes. > > > > > > > FluintListener runs all the fluint tests and then iterates over > > the > > > > > > results calling all the appropriate sockerReporter methods. There's > > also a > > > > > > way to extend the fluint TestRunner and call the sockerReporter > > methods as > > > > > > the tests are finishing, but I think what I have right now is the > > simplest > > > > > > solution. > > > > > > > Have never contributed to an open source project before, so just > > attaching > > > > > > the source in this email. > > > > > > > Eugene --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
