Mike Williams wrote:
David Kemp wrote:
we could leave the default behaviour as is, but support both "trim"
and "untrimmed" for those wanting to be explicit about it.
assertValue | foo | untrimmed:tolower:regexp:^fo*$
I'd been thinking that stacked prefixes would be similar to nested
funct
Hello,
I use custom in my selenium tests. I was surprised that whereas it is
permitted to use whatever (javascript permitted) character with whatever
case in custom function names ([A-Z].+ in selenium-browserbot.js, line
376), selenium runner only permits you to use [a-z] low cases.
I don't u
Excuse me for the last patch won't work for selenium wont recognize
implicit locators anymore (which I don't use).
It's better to limit character for locator type to [a-zA-Z_]
so the new patch :
Index: selenium-browserbot.js
===
Hello,
I am requesting an MD5 checksum for selenium-0.5.0.zip file from
http://gforge.public.thoughtworks.org. Due to security requirements, I
am required to obtain digital signatures on downloads before
installation in-house. Your assistance is greatly appreciated.
Thanks-
Amanda
--
Respectful
Apologies in advance for the long, dull novel.
> This is not exactly a bug - more a limitation of the design. At the
> moment, element locators are expected to return only a single element.
> This works nicely for most cases, but as you've found, it makes it
> trickier to deal with groups of rad
