In fact, to verify tests against multiple browsers, don't have to run one test the same time for 3 browsers (can be done, though). Besides maintainability, the other test automation challenge is long execution time (Google average build time: 4 minutes, http://blog.utest.com/testing-the-limits-with-patrick-copeland-part-i/2010/02/). We configured our CI server to distribute tests to different build agents (we use BuildWise Agent, http://testwisely.com/en/buildwise/downloads, you can customize your Selenium-Grid), which set to run different browsers (Firefox, Chrome). As the test assigned to different build agents for every build, essentially, all browsers are covered without sacrificing the performance.
-- -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected] --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
