[
https://jira.jboss.org/jira/browse/RF-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496331#action_12496331
]
Lukas Fryc commented on RF-8026:
--------------------------------
I configured new job, which uses richfaces-demo-3.3.3-jsf2-SNAPSHOT:
http://hudson.qa.jboss.com/hudson/view/web-ui-temp/job/richfaces-3.3-jsf2-demoapp-ftest-firefox-linux-sandbox
(VPN only)
> Selenium: create compatibility layer checking standard components' conditions
> ------------------------------------------------------------------------------
>
> Key: RF-8026
> URL: https://jira.jboss.org/jira/browse/RF-8026
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: functional-tests, JSF 2.0
> Affects Versions: 3.3.3.BETA1
> Reporter: Nick Belaevski
> Assignee: Lukas Fryc
> Fix For: 3.3.3.BETA1
>
> Attachments: demo.patch, jsf2-error1.html
>
>
> After upgrade from JSF 1.2 to 2.0 it appeared, that checks for standard
> components (e.g. existence of generated Faces messages) are not working
> properly due to changes in JSF renderers.
> I'd suggest to create separate project that will contain base check methods
> compatible with both JSF 1.2 and 2.0 and use it for all functional tests. It
> can be even covered by unit tests running Selenium tests in HtmlUnit
> environment (Selenium reference card from DZone refers to this as a means of
> tests execution speed optimization)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
