[richfaces-planning-issues] [JBoss JIRA] Commented: (RFPL-1634) Determining impact of JQuery update

Juraj Huska (JIRA) jira-events at lists.jboss.org
Mon Sep 5 12:00:26 EDT 2011


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

Juraj Huska commented on RFPL-1634:
-----------------------------------

I have built jQuery branch as said above and also used compatibility mode to verify showcase IE9 JIRAS with results described in RFPL-1632.
I have also relabeled all JIRAS according to the whether it was solved by upgrading or using compatibility mode with labels described also in RFPL-1632.

> Determining impact of JQuery update
> -----------------------------------
>
>                 Key: RFPL-1634
>                 URL: https://issues.jboss.org/browse/RFPL-1634
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: QE
>    Affects Versions: 4.1.0.Milestone2
>            Reporter: Lukáš Fryč
>            Assignee: Juraj Huska
>            Priority: Critical
>             Fix For: 4.1.0.Milestone2
>
>
> jQuery Upgrade: (RF-10882) 
>     • The jQuery upgrade broke some unit tests, which were resolved by upgrading htmlunit. I added comments to RF-11360 outlining the unit tests that break before and after the htmlunit upgrade (jsf-test version 6 vs. 7). 
>     • QE: Can you look at those broken lists, and determine in which scenario we are better covered by the QE functional tests? IOW, which set of unit tests are we better off ignoring due to functional test coverage? 
>     • Once this is determined, we will merge the jQuery upgrade branch into develop 
> IE 9 Tests: (RFPL-1599) 
>     • There is an JSF issue that breaks ajax with Internet Explorer 9 in "normal mode". I made a note of this in the comments of RF-11266 
>     • QE: can you verify which of our IE 9 issues are still present when running IE 9 in "compatibility mode"? Maybe relabel the ones that are only broken in normal mode with the label: "ie9_normal" 
>     • Hopefully with this, we can close (or defer) a significant number of M2 issues 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the richfaces-planning-issues mailing list