My colleagues in QA are having better results with Selenium + FlexMonkium
than with FlexMonkey + 3.5.
But FlexMonkium apparently only supports Flex 4.

I have been cautious/wary about proposing an upgrade to Flex 4 at this time,
particularly since I encountered a ComboBox bug introduced in 3.5 when I
upgraded to get fixes for charting bugs in 3.4. But a solid automation story
would be quite compelling.

So I guess I'm looking for reassurance, and also wondering a few things.

Is there some bug fix in automation libraries that makes it more robust even
if you're using Halo components?
What's compatibility mode and why would I use it?

Thanks.

Reply via email to