On Thu, August 25, 2005 9:11, Jamo Smith said:
> HOWDY!
>
> I wrote my own assertElementOrder a few months back and today I finally
> updated to the newest version 0.5 of selenium (from 0.3).
>
> So I moved my custom assertion into the user-extensions.js as instructed.
> However it no longer works.
I don't have the Selenium source-code in front of me right now, so please
excuse me if this is an under-informed response.
Looking at your code, it LOOKS like you're doing the right thing.
The error you're getting suggests that
this.page().findElement("//a[text()='Locked Topic']")
is failing. However, the fact that the previous "assertElementPresent"
command worked tells a different story.
Perhaps your command is passing a leading space to findElement()? ie.
this.page().findElement(" //a[text()='Locked Topic']")
I can only suggest inserting some calls to LOG.info(), to investigate
where it's going wrong. The log will appear under the AUT frame ...
you'll have to scroll the page down to see it.
--
cheers, Mike
_______________________________________________
Selenium-devel mailing list
Selenium-devel@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
