You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Carlin Rogers (JIRA)" <be...@incubator.apache.org> on 2005/05/10 20:36:12 UTC

[jira] Commented: (BEEHIVE-633) UpdateFormFromNestedPopup BVT test fails on Certain Type of Machines

     [ http://issues.apache.org/jira/browse/BEEHIVE-633?page=comments#action_64882 ]
     
Carlin Rogers commented on BEEHIVE-633:
---------------------------------------

The test failure is due to a bug in the HtmlTag rendering class.
The clear() method of the inner class, State, did not call
clear() on its super class, AbstractAttributeState. Therefor
the general map in the HtmlTag State was never cleared, leaving
the registered attribute for the "netui:idScope" in the state.

So the test recording, UpdateFormFromNestedPopup, had false 
"netui:idScope" attributes on the html tag. In this test they
should not be there. They appear due to the issue described
above where the state was not cleared. To reproduce, you can
go to the Controller of the UpdateFormFromNestedPopup test,
/coreWeb/miniTests/updateFormFromNestedPopup/Controller.jpf,
and then look at the page source. No "netui:idScope" attribute,
which is correct (I.E. the test recording should not have the
scoped Id). Then hit the JSP for the MockPortalPopupWindows
test which is in the same page flow.
http://localhost:8080/coreWeb/miniTests/updateFormFromNestedPopup/MockPortal.jsp
Now go back to the original Controller for the 
UpdateFormFromNestedPopup test and look at the source again.
The html tag will now have the "netui:idScope" attribute!
However, it should not. It's there because the state was
not cleared. 

I'm going to attach a patch to fix the state issue as well
as fix the recorded UpdateFormFromNestedPopup test so that
it does not expect the bogus "netui:idScope" attributes on
the html tags.

> UpdateFormFromNestedPopup BVT test fails on Certain Type of Machines
> --------------------------------------------------------------------
>
>          Key: BEEHIVE-633
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-633
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Julie Zhuo
>     Assignee: Carlin Rogers
>     Priority: Minor
>  Attachments: clearstate.txt
>
> Have run the netui bvt tests on a couple of DELL530, one has W2K and the other Linux(2.4.21-27.EL). It actually fails on both configurations. It seems not generating idScope. Here is the testRecorder diff,
> <dif:testNumber>5</dif:testNumber> 
>   <dif:uri>/coreWeb/miniTests/updateFormFromNestedPopup/submit.do</dif:uri> 
>   <dif:diffResults>Line (3) does not match. R: <html lang="en" netui:idScope="portletA"> P: <html lang="en"></dif:diffResults> 
>   </dif:request>
>   </dif:recorderDiff>
> Repro: Run netui bvt test in svn tree on the above machine type and configurations. It seems the machine type really causes the problem. :)
> ** Will comment out this test from the distribution BVT tests with CR number attached. I believe at some point we need to turn this test back on. :)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira