1 person found this helpful
If the subcomponents are Sprite but the main component is a UIComponent, the
main component should be usable in the automated testing. The issue will be
what the subcomponents mean to the test. For example, DataGrid is a
UIComponent whose renderer children don't have to be UIComponents and
default to being TextFields.
If the main component is more like a Container, you'll probably have more
work to do and it might just be easier if your subcomponents were custom
UIComponents. You might be able to disable some of the APIs that slow down
UIComponent compared to Sprite.
Yes, the main component is a UIComponent.
I'll look into the DataGrid delegate to see how it deals with non UIComponent elements.
I'm pretty sure we won't replace Sprite for UIComponents because performances is one of the reasons
why people buy this component instead of similar ones in the market. And I don't think we will get
similar performances with UIComponents even if we tweak them.
So the nice guys on RIATest forum helped me on that subject, so I thought it would be interesting to update this post
since it could interest other people.
This is because getClassInfoXML does not define automationName. This should fix it:
public static function getClassInfoXML(): XML
return <ClassInfo Name="CustomClass" Extends="FlexDisplayObject">
<Property Name="automationName" Describes="true">
<Property Name="automationClassName" Describes="true" Doc="The class name as it is known to RIATest.">
<Property Name="className" Describes="true" Doc="Internal Flex class name.">
<Property Name="automationIndex" Describes="true">
<Property Name="numAutomationChildren" Verify="true" Doc="Number of automation children of this object.">