Jamie Orchard-Hays wrote:
I can cause it to fail in the same test rather than the next test. I'll include an html results set of a suite of four tests to show you what I mean. The "halt" command is a custom one. If I leave it out, then the failure is usually on the next test.
Yup. That's what I'd expect (ie. that's consistent with the bug that I've observed). As it stands, Selenium checks for unexpected alert/confirmations immediately before executing a command. By adding your call to "halt", you enable the check to occur.
-- cheers, MikeW http://www.dogbiscuit.org/mdub/ _______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
