Hi, thanks for your reply.
David Kemp wrote:
Back in October, in the e-mail "Grand plans (0.7 and beyond)", Mike
Williams wrote:
DavidK is part-way
through a refactoring which should make it possible for drivers to
actually retrieve useful data from the browser, rather than just lobbing
it "assert" commands. It would be super-cool if we could support a
Watir-compatibile API.
The work I did that Mike is referring to is to automatically generate
assert, assertNot, verify, and verifyNot commands from any functions of
the form getXXX() and getXXX(arg). My initial objective was to also
automatically generate store, waitFor, and waitForNot commands from all of
these methods, but I have not got around to it yet. The framework
currently also automatically generates "get commands" from these methods,
but I do not think anything can actually use "get commands" yet. If
someone is interested in posting a patch that lets you do this, then I
imagine there would be lots of people interested in it!
I don't think I understand what you're saying here. Can I ask a few
questions to clarify?
1) I've only ever used the Java driver, but it was my understanding that
some of the drivers (Ruby, at least, and probably Plone) already
auto-generated their commands based on the selenium-api JavaScript, but
that some of the drivers don't do that (Java, at least, and probably
.NET).
Is it true that Ruby/Plone auto-generate driver commands based on the
JavaScript but Java/.NET don't?
2) As far as you know, do the "get" commands work on all drivers? If not,
on which drivers do you think they're broken? On which drivers do you
think they work?
FYI, the official 0.6.0 Java Driver doesn't work on IE or Netscape, but
Nelson and I have filed bugs and submitted patches to make it work. (The
biggest issue was a caching bug: SEL-168, SEL-173.) Beyond getting the
Java Driver to work in the first place, we haven't noticed any problems
with the Java get* commands; they're part of the RealDealIntegrationTest,
which passes once you fix SEL-168.
3) Peering through FishEye, It looks like most of this work happened in
August, and it looks like that code got in to 0.6.0. Are you still
actively working on this? Is it safe for me to wander in and start
fooling around with it?
-Dan
-unless you love someone-
-nothing else makes any sense-
e.e. cummings
_______________________________________________
Selenium-devel mailing list
Selenium-devel@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
