[ 
https://issues.apache.org/jira/browse/FLEX-29806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445993#comment-13445993
 ] 

Bertrand Delacretaz commented on FLEX-29806:
--------------------------------------------

I have removed the installer from this issues' list of components, feel free to 
revert if that was wrong.
                
> Automation is busted for custom components that are contained by parents that 
> are based on UIComponent
> ------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-29806
>                 URL: https://issues.apache.org/jira/browse/FLEX-29806
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Active Screen, AgentAPI, Checkpoints, Component 
> Dispatch, Component Replay, Descriptive Programming, Documentation, Framework 
> Sync, Mercury sync, XMPPStream API
>    Affects Versions: Adobe Flex SDK Previous
>         Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>            Reporter: Adobe JIRA
>
> Steps to reproduce:
> 1. Create custom component A, that is automateable and implement all of 
> IAutomationObject, ensure showInAutomationHierarchy = true
> 2. Create custom component B, that is not automateable and inherits from 
> UIComponent, ensure showInAutomationHierarchy = false
> 3. Create custom component C, that is automateable and implement all of 
> IAutomationObject, ensure showInAutomationHierarchy = true
> 4. Create instance of A, B and C.  A contains B which contains C.
> 5. Try using a QTP feature, such as object spy
>  Actual Results:
> QTP can't see C 
>  
>  Expected Results:
> QTP can see C 
>  
> The problem is because in various places in constructing C's automationId, it 
> ignores the showInAutomationHierarchy flag, and expects component B to create 
> an ID for C, which is invalid.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to