[JBoss JIRA] Created: (RFPL-1634) Determining impact of JQuery update
by Lukáš Fryč (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: 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
14 years, 7 months
[JBoss JIRA] Created: (RFPL-1639) htmlunit version decision
by Brian Leathem (JIRA)
htmlunit version decision
-------------------------
Key: RFPL-1639
URL: https://issues.jboss.org/browse/RFPL-1639
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Leathem
The jQuery upgrade broke some unit tests, which were resolved by upgrading htmlunit.
Running the build against both versions 1.0.6 and 1.0.7-SNAPHOST of jsf-test, I found the following tests break (copied from RF-11360).
h2.The tests that fail with jsf-test 1.0.6:
[INFO] Richfaces UI Components: Output UI ................ FAILURE [33.269s]
Tests in error:
testServerClick(org.richfaces.renderkit.html.DropDownMenuRendererTest)
{code}TypeError: Cannot find function removeAttributeNode in object [object]. (http://localhost:0/javax.faces.resource/jquery.js.jsf#2282){code}
testServerClick(org.richfaces.renderkit.html.MenuItemRendererTest)
{code}Cannot find function removeAttributeNode in object [object]. (http://localhost:0/javax.faces.resource/jquery.js.jsf#2282){code}
h2.The tests that fail with jsf-test 1.0.7-SNAPHOST:
[INFO] Richfaces UI Components: Iteration UI ............. FAILURE [37.160s]
Failed tests:
testOutDataScrollerFirstLastButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[a]> but was:<[span]>{code}
testInnerDataScrollerFirstLastButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[a]> but was:<[span]>{code}
testOutDataScrollerNextPreviousButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[span]> but was:<[a]>{code}
testInnerDataScrollerNextPreviousButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[span]> but was:<[a]>{code}
testOutDataScrollerFastButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[span]> but was:<[a]>{code}
testInnerDataScrollerFastButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[span]> but was:<[a]>{code}
testOutDataScrollerDigitalButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[span]> but was:<[a]>{code}
testInnerDataScrollerDigitalButtons(org.richfaces.renderkit.DataScrollerRenderTest)
{code}org.junit.ComparisonFailure: expected:<[span]> but was:<[a]>{code}
[INFO] Richfaces UI Components: Input UI ................. FAILURE [1:30.258s]
Failed tests:
testListLayoutRender(org.richfaces.renderkit.AutocompleteRendererTest)
{code}
[not identical] Expected attribute value 'form:myAutocompleteInput' but was 'form:myAutocomplete' - comparing <input name="form:myAutocompleteInput"...> at /span[1]/span[1]/input[1]/@name to <input
name="form:myAutocomplete"...> at /span[1]/span[1]/input[1]/@name
{code}
testDivLayoutRender(org.richfaces.renderkit.AutocompleteRendererTest)
{code}
[not identical] Expected attribute value 'form:myAutocompleteInput' but was 'form:myAutocomplete' - comparing <input name="form:myAutocompleteInput"...> at /span[1]/span[1]/input[1]/@name to <input name="form:myAutocomplete"...> at /span[1]/span[1]/input[1]/@name
{code}
h2. The task at hand
Based on the above failing tests, we need to determine which tests are better covered by the QE functional tests, and decide which is the better version of htmlunit for us to use moving forward.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (RFPL-1633) Pre-release testing of rich:editor
by Lukáš Fryč (JIRA)
Pre-release testing of rich:editor
----------------------------------
Key: RFPL-1633
URL: https://issues.jboss.org/browse/RFPL-1633
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
Editor has been greatly refactored in scope of M2 and it would be great to do release-wide testing before end of M2, this includes:
* smoke testing of editor on all supported containers
* complete testing of all features of editor in all supported browsers
* smoke test with all available skins focusing on readability and usability in all supported browsers
Please note your plan on testing matrix.
Changes that may affect testing:
* new 'richfaces' skin (made default)
** skin consistent with RichFaces component suite skins
** skinned main editor interface + popups
** popups should have consistent look with rich:popupPanel
* configuration through {{@config}} attribute or {{<f:facet name="config">}}
* new attributes/facets ({{skin, config, lang, ondirty}})
[Complete list of fixed issues for editor in M2|https://issues.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuer...]
This testing should minimize the risk of introducing such fundamental changes in second milestone.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months