Hi all,

John & Pip .. thx!  I too hope I can get this thing to work.

Actually, I should have included the full details of the error report for
Marc.  Don't know what I'm thinking.
Here it is:

Details javascript errorReferenceError: "CollectGarbage" is not defined. (
http://s.bebo.com/script/mootools.v1.11.js#3(eval)#1)  line1  javascript
source function () { window.addListener("unload", Garbage.empty); if (
window.ie) { window.addListener("unload", CollectGarbage); } }  failing line
 javascript call stackReferenceError: "CollectGarbage" is not defined. (
http://s.bebo.com/script/mootools.v1.11.js#3(eval)#1) at (
http://s.bebo.com/script/mootools.v1.11.js#3(eval):1)
Again, this comes out of our mootools library, which you will see in the
header of aforementioned bebo site
InviteJoin page.

On 3/4/08, Marc Guillemot <[EMAIL PROTECTED]> wrote:
>
> As you've checked that no js error occurs in "real" browser, this seems
> to be an issue with WebTest JS support.
> WebTest JS support (in fact HtmlUnit's one) gets continuously better but
> is still not 100% as good as it should be.
>
> 2 questions:
> - which WebTest version do you use?
> - if this is the latest one, do you have a publicly available website
> where the problem can be reproduced? This would allow to understand and
> fix it.
>
> Cheers,
> Marc.
> --
> Blog: http://mguillem.wordpress.com
>
>
> Ken Hopf wrote:
> > Hi,
> >
> > I'm new to WebTest, so perhaps this is just a silly question on my
> > part.  I'm running my first WebTest and everything is humming along
> nicely,
> > until I try to click a final submit button, at which point I get the
> > following error:
> >
> > javascript errorReferenceError: "CollectGarbage" is not defined.
> > (http://s.bebo.com/script/mootools.v1.11.js#3(eval)#1)
> >
> > This mootools thing is an Ajax library we use here at Bebo.  Now, when
> > we run the page interactively, there's no visible problem.  But, it
> seems
> > to me that, despite what engineering tells me, this particular error is
> > not the fault of WebTest but rather of the ajax library (which
> unfortunately
> > is compressed).
> >
> > I thought that perhaps a WebTest expert might have some insight about
> > the issue ... eg, whether this really is a problem with WebTest and,
> > whether it is not, any ideas about dealing with it???   For instance,
> > does it make sense to anyone that this thing might work fine
> interactively,
> > but fail when invoked by WebTest ??   If it is really a problem in the
> > target application, is there any way to suppress the error aside from
> > changing the source code ??
> >
> > Thanks in advance,
> > Ken Hopf
>
>
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>

Reply via email to