[richfaces-planning-issues] [JBoss JIRA] Assigned: (RFPL-1639) htmlunit version decision

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 Assignee: Ján Jamrich 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.