On Tue, 27 Jun 2006 07:52:43 -0400, Paul Field <[EMAIL PROTECTED]> wrote:
One other thing is that the "Selenium" object that represents your session is very expensive to create (it requires creating an instance of the web browser). You can use JUnit setUp/tearDown around a suite so that you only create it once (or use @BeforeClass/@AfterClass in Junit 4). However, I've found that with @BeforeClass/@AfterClass you have suite==class and all your tests for the session need to be in one class. I've found that TestNG's concept of a suite is much more suitable as it can span multiple classes and you can its 'groups' concept to run subsets of the tests (http://testng.org/).
Thanks for the info. I'll be using TestNG, so that front doesn't sound like it'll be an issue. Firing up the Web browser, on the other hand, may be. Do you happen to have any experience setting this up on a headless build server? I realize this is going way OT, so if you want to take it off the list, feel free.
Thanks, Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
