Luke Closs wrote:
What about a more general 'skip' feature. Test cases or individual
commands could be skipped based on some test. I see this in perl test
suites all the time, something like:
unless package foo is installed {
skip all tests
}
In the interests of keeping things simple, perhaps we could first
limit this skip ability to a whole test case html file.
Apologies if I'm repeating myself, but I don't think it's worth
attempting to support conditional logic in Selenium's table-driven mode.
(Similarly for loops, or gotos, or "macros" etc). It's a slippery
slope: first we support conditional tests, then conditional commands,
then someone wants to make "groups" of commands conditional, and someone
else requests an if..then..else construct, and we're on our way to
creating yet another crappy scripting language. For a good exploration
of this topic, see
http://www.stickyminds.com/sitewide.asp?ObjectId=2326&ObjectType=COL&Function=edetail
What I was suggesting was different - rather than the *tester* telling
Selenium not to execute a certain assertion (in a given environment),
I'm suggesting that *Selenium* could tell the tester that the assertion
isn't supported (in that environment) ... but without "failing" the test.
--
cheers, MikeW http://www.dogbiscuit.org/mdub/
_______________________________________________
Selenium-devel mailing list
Selenium-devel@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
