[richfaces-planning-issues] [JBoss JIRA] (RFPL-3195) Stabilize Framework Tests on supported containers

[Jiří Štefek (JIRA)]

    [ https://issues.jboss.org/browse/RFPL-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12939314#comment-12939314 ] 

Jiří Štefek commented on RFPL-3195:
-----------------------------------

Some notable notes I forget to put here:

ITTestJsFunction:
the test was failing on WildFly but not on EAP
The problem was in listener method of backing bean. there is a different behaviour between containers:
* EAP 6.1.0: no listener method is invoked, but param IS passed to bean
* WildFly: error javax.el.MethodNotFoundException: Method not found: org.richfaces.ui.ajax.AjaxBean at 426dc56c.listener() is thrown and param IS NOT passed to bean

Resolution: the bean has to contain a proper listener method: either listener(ActionEvent event) or listener().
----

ITPanelMenu:
* ok on EAP
* on Wildfly:
{code}
java.lang.RuntimeException: Could not inject members
java.lang.IllegalArgumentException: Can not set org.richfaces.ui.toggle.panelMenu.PanelMenuBean field org.richfaces.ui.toggle.panelMenu.VerifyMenuAction$DidOccur.panelMenuBean to org.richfaces.ui.toggle.panelMenu.VerifyMenuAction$DidOccur
{code}
Seems that it was injecting the wrong instance to the field. Resolution: imported both classes from static class to WAR.
                
> Stabilize Framework Tests on supported containers
> -------------------------------------------------
>
>                 Key: RFPL-3195
>                 URL: https://issues.jboss.org/browse/RFPL-3195
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: QE
>            Reporter: Lukáš Fryč
>            Assignee: Jiří Štefek
>             Fix For: 5.0.0.Alpha3
>
>
> Lot of tests are currently failing on EAP and WildFly:
> https://gist.github.com/lfryc/962b0eab11e8d0536a33
> We should stabilize the tests on containers where we expect 100% compatibility - JBoss EAP 6.2 at the moment, so we could use the tests for regression testing.
> We should either:
> 1) fix a framework test
> 2) find an framework issue and report it
> Subsequently we may want to mark some tests as Failing or FailingOnCertainEnvironment, but that is preliminary atm.

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