4:31 a.m.
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: Ján Jamrich
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
4:33 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1634) Determining impact of JQuery update
[
https://issues.jboss.org/browse/RFPL-1634?page=com.atlassian.jira.plugin....
]
Lukáš Fryč updated RFPL-1634:
-----------------------------
Priority: Critical (was: Major)
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: Ján Jamrich
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
6:38 a.m.
New subject: [JBoss JIRA] Updated: (RFPL-1634) Determining impact of JQuery update
[
https://issues.jboss.org/browse/RFPL-1634?page=com.atlassian.jira.plugin....
]
Juraj Huska updated RFPL-1634:
------------------------------
Assignee: Juraj Huska (was: Ján Jamrich)
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
11 a.m.
New subject: [JBoss JIRA] Commented: (RFPL-1634) Determining impact of JQuery update
[
https://issues.jboss.org/browse/RFPL-1634?page=com.atlassian.jira.plugin....
]
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
11:02 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RFPL-1634) Determining impact of JQuery update
[
https://issues.jboss.org/browse/RFPL-1634?page=com.atlassian.jira.plugin....
]
Juraj Huska edited comment on RFPL-1634 at 9/5/11 12:01 PM:
------------------------------------------------------------
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 IE9 JIRAS (RFPL-1599) according to the whether it was solved by
upgrading or using compatibility mode with labels described also in RFPL-1632.
was (Author: jhuska):
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
8:27 a.m.
New subject: [JBoss JIRA] Commented: (RFPL-1634) Determining impact of JQuery update
[
https://issues.jboss.org/browse/RFPL-1634?page=com.atlassian.jira.plugin....
]
Ján Jamrich commented on RFPL-1634:
-----------------------------------
Conclusion from my side (verifying impact of change by functional testing by our selenium
tests) is that this upgrade impact only rich:editor component (editor doesn't
display). All other test failures are not related to this change.
(Sorting problem in extendedDataTable as I described above appears in Metamer with older
jquery version as well).
Appropriate JIRA for problem with editor found is filled and linked to this JIRA.
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
6:11 p.m.
New subject: [JBoss JIRA] Resolved: (RFPL-1634) Determining impact of JQuery update
[
https://issues.jboss.org/browse/RFPL-1634?page=com.atlassian.jira.plugin....
]
Brian Leathem resolved RFPL-1634.
---------------------------------
Resolution: Done
jQuery upgrade branch merged
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
5345
days inactive
5348
days old
richfaces-planning-issues@lists.jboss.org
6 comments
4 participants
participants (4)
-
Brian Leathem (JIRA) -
Juraj Huska (JIRA)
-
Ján Jamrich (JIRA)
-
Lukáš Fryč (JIRA)