Hi Ken, You may want to consider refactoring your tests to run in a single script. (Or have two scripts, but copy the first one into the second).
It's generally good unit-testing practice to have all setup/teardown operations done (or at least called) within each individual script. The reason for this is that when you do get an error in the second script, you're not immediately sure of whether the error actually was in the second script, or if something didn't happen properly with your first script. If you had things separated, you'd immediately know if you had a problem creating the user account, if the problem was logging in later with a valid account. I'm doing something similar to this using #include statements and it seems to be working well enough. - Peter Bernier _______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
