Selenium's own self-test suite is in fact four separate suites: one each
for Firefox, IE, Konqueror and Safari. I find this duplication mildly
irritating, and certainly it's not easy to see (at a glance) what
Selenium functionality is unsupported on each platform.
I suspect that this would also be an issue for real live cross-browser
test-suites. For example, I have some tests for visibility of elements
in my app. Currently I'm just running the tests in IE, but if I wanted
to do cross-browser testing, I'd need to find a way to suppress those
One approach is to do this outside Selenium: serve up suites and tests
tailored to the target browser environment.
As an alternative though, here's a wacky idea: we could introduce a
"soft" assertion failure state: "unsupported", which means that nothing
actually failed, but Selenium doesn't support that particular assertion
in the current browser. The "unsupported" result would bubble up to
infect the enclosing test and suite, unless trumped by a failure or error.
What do you think? A useful feature, or overkill?
--
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
