[richfaces-planning-issues] [JBoss JIRA] (RFPL-2751) Metamer: rich:dropTarget: all tests fails within richCollapsibleSubTable template

[Ján Jamrich (JIRA)]

     [ https://issues.jboss.org/browse/RFPL-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ján Jamrich updated RFPL-2751:
------------------------------

    Issue Type: Bug  (was: Feature Request)
      Assignee:     (was: Lukáš Fryč)


Quickk fix - exclude richCollapsibleSubTable from testsuite for dropTarget is not solution, just workaround. So creating this issue to keep record and effort to fix it.
                
> Metamer: rich:dropTarget: all tests fails within richCollapsibleSubTable template
> ---------------------------------------------------------------------------------
>
>                 Key: RFPL-2751
>                 URL: https://issues.jboss.org/browse/RFPL-2751
>             Project: RichFaces Planning
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: testing
>    Affects Versions: 4.3.0.Final
>         Environment: accross containers, browser FF
>            Reporter: Ján Jamrich
>         Attachments: screenshot-dnd-dropTargetFailure.png
>
>
> Run dropTarget tests (using webDriver) within all templates it fails every time for TestDropTarget when testing within richCollapsibleSubTable, even in other templates can pass, and run this test only within richCollapsibleSubTable template passed too.
> There is example job using jbas-71 container to simulate this behavior.
> Analyzing screenshots/observing job during test using VNC realized ERROR status after drop event performed, while drop action not processed, so all tests fails on waiting for element created on drop accept process (it is bellow the drop area, and displays attributes of dropped object).
> For more info see referenced job using jbas-71 and all templates [1]
> [1] http://hudson.qa.jboss.com/hudson/view/RF-QE/job/richfaces-metamer-ftest--server-compatibility-dnd-jbas71/4/

--
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