I have just committed code that automatically generates asserts, assertNots, verify, and verifyNots from getters.
For example, I have deleted selenium-api:assertValue() and replaced it with selenim-api:getValue()
So, in addition to the old assertValue and verifyValue, we now also have assertNotValue and verifyNotValue.
Still to do:
- Replace more of the existing commands (e.g. assertText, assertTitle, etc.)
- Automatically generate waitForX, waitForNotX, and storeX commands.
- Do something similar for boolean functions (e.g. isTextPresent).
I probably will not have time to do much for a couple of weeks other than a little bit of cleaning up of what I have done so far.
Can anyone see any problems with what I am attempting to do?
Also, I am not all that confident with the implementations of AssertHandler, AssertHandlerUsingAccessor, and NegativeAssertHandlerUsingAccessor. I still find _javascript_ class inheritance a little strange, and so would welcome suggestions on how to improve how these work... or just go ahead and improve them :-)
Cheers,
David
David Kemp
ThoughtWorks Australia Pty Ltd
http://www.thoughtworks.com
_______________________________________________ Selenium-devel mailing list Selenium-devel@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
