I have just updated the documentation to include some new commands that are included in release 0.6, but of course the new documentation will not be released until we get to release 0.7 :-(
They are a number of negative assertions available as a result of the work I have been doing on generalising the command generation and include:
assertNotTitle, assertNotValue, assertNotText, assertNotAttribute, and assertNotTable.
They each take a pattern, and succeed only if the supplied pattern does NOT match the value specified in the target.
Be careful though, they will fail if the specified target does not exist.
For example the following will only succeed if there is an element with the id of "foo", with an attribute called "src", and the value of that "src" attribute does not end in "bar". If there are no elements with the id of "foo", or if there is such an element but it does not have an attribute called "src", then the test will fail. If there is more than one element with an id of "foo" then the success or failure will depend entirely on which one Selenium happens to choose (which is not defined).
verifyNotAttribute | [EMAIL PROTECTED] | *bar
I think that this is the behaviour we want to support, but am happy to listen to objections (but perhaps that sort of discussion belongs on the developers mailing list?)
A separate issue is the form of these commands. For example, it might be more grammatically natural to use "assertValueNot" than "assertNotValue". Supporting both would actually be quite trivial, but again, such a discussion probably belongs on the developers mailing list.
David Kemp
ThoughtWorks Australia Pty Ltd
http://www.thoughtworks.com
_______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
