FW: [Webunitproj-users] unit tests failing

[<Eri...@al...>]

All,

Here is a list of my latest changes, all committed to CVS.
Most notably,=20
a) the unit tests are working again.
b) IFrameTest shows how to deal with html controls dynamically generated
onto an <IFRAME>.


--SelectTest was ommitted from WebUnitSuite (whoops).  added it back in.
--Now loading <iFrame/> tags just like <Frame> tags.  This enables
client API=20
  to access controls added by javascript at runtime (document.write() ).
See the JUnit test IFrameTest for details.  Erik O.
--Added target to build file to run unit tests with debug: unittestd
(use unittest to run w/o debug). Erik O.
--Added assertEnabled and assertDisabled to WebUnitTest.  These enable
you to encode=20
  (with just a single line of java) an expectation that a particular
html control (a WebTag) is either enabled or disabled.  Erik O.
--When I applied patch 628620, I broke the unit tests.  The 'onchange'
event
  was firing for controls that don't support it.  Fixed in
ExplorerNativeWebClient.setOption(). Erik O.
--exposed WebClient#clearCache().  This method was in the impl, but not
in the interface.
  After manipulating html controls dynamically generated onto an
<IFRAME>,
  I used this method to enable me to access, once again, the frame's
parent DOM.
  Without calling this method, I was stuck mucking around with the data
on the child IFRAME.
  See IFrameTest for an example.
  Thanks Doron for the high level design suggestions.    Erik O.
--Added a convenience method to the
WebForm/DefautlWebForm#getSubmitButtonWithId() Erik O.
--Couldn't setText() for <input type=3Dpassword/>.  To fix it, commented
out one line in ExplorerNativeWebClient.java:
//ivCompArgs.put("value","");
  There is a more indepth comment at the commented out line.  Erik O.

Unfortunately, we still have the intermittant failure on the first test
when
running 'ant unittest'. Remember, just run it 2-3 times and the errors
clear up.
Let me know if I broke anything.

Next, I'll do some more work with Brian K's most recent patch.

Thanks,
--Erik

      > -----Original Message-----
      > From: Ostermueller, Erik=20
      > Sent: Wednesday, November 20, 2002 5:09 PM
      > To: bt...@ne...; web...@li...
      > Subject: RE: [Webunitproj-users] unit tests failing
      >=20
      >=20
      > Brian,
      >=20
      > My apologies.  I believe the current CVS is indeed=20
      > broken -- that is,
      > the unit tests don't run correctly.
      >=20
      > I'm not sure how it slipped by, but I broke it.
      > I applied patch  628620; removing it fixes things.
      > I'll get to work on this first thing tomorrow.
      > It would be helpful if anyone could confirm this for me.
      > steps: download the latests CVS, build and then run=20
      > the unit tests by calling 'ant unittest'.
      >=20
      > Here are the errors I'm getting.  Brian, they look
      > similar to what you got.
      >=20
      > One very odd thing is that this patch was for setOption().
      > Option controls arn't even part of the
      > com.zeborg.webunit.EnableDisableTest.
      > I'll give you all an update tomorrow.
      >=20
      > --Erik
      >=20
      >=20
<<snip>>