I have read in few messages that there are some cases that are not testable with the iTest flex wrapper, though they're relativley rare..
What are those cases ?
Answer by koelze · Jun 11, 2012 at 06:51 PM
I'm not sure this is going to be a perfect enumeration of all of the issues, but in general, the reasons why things aren't testable with the Flex wrapper are because the product under test is something that relies (either explicitly or implicitly) on the assumption that the product is going to be at the top level of the hierarchy. Let me give you a couple of different examples that I've seen:
I saw an application that at one point in it made a typecast on the Window.window object to a specific type. When running not through the Flex Wrapper, this worked fine, because the Window.window object did actually refer to the application, but under the wrapper, this was an illegal cast, because the top level window object was the Flex Wrapper when embedded.
I also saw another application that did some dynamic resource loading at its top level, but made an assumption somewhere else that this resource was loaded into the actual top level; because it was embedded in a FlexWrapper, this ended up not working as intended when embedded.
In general, the ones I've seen tend to be of this variety, because the major difference when using the Flex Wrapper is that your application ends up not being that top level window object.
Copyright 2008- Spirent Communications, all rights reserved. Terms and Conditions.