All, I'd like to suggest some improvements to the tapestry-test library. I've had to write my own custom version of these classes because some of them aren't very configurable.
- Perhaps most importantly, leverage the @BeforeSuite and @AfterSuite TestNG annotations for setting up and tearing down the environment. Surefire has <finally> begun supporting these annotations in their most recent releases. That way one could use a single browser instance for all tests. - Allow a "browser" TestNG parameter to dynamically configure which browser the tests run on. That way you're able to test multiple browsers immediately and painlessly: <!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd";> <suite name="seleniumTests"> <test name="IEFunctionalTests"> <parameter name="browser" value="*iexplore"/> <packages> <package name="com.mycompany.app.functest" /> </packages> </test> <test name="FireFoxFunctionalTests"> <parameter name="browser" value="*firefox"/> <packages> <package name="com.mycompany.app.functest" /> </packages> </test> </suite> - A method to typeWithFullKeyEvents would greatly enhance AJAX testing, something similar to the method found here: http://blogs.atlassian.com/developer/2007/08/selenium_is_the_pain_worth_ it.html - I've found a need to configure member variables that aren't configurable, like AbstractIntegrationTestSuite.BASE_URL and JettyRunner.DEFAULT_SECURE_PORT, JettyRunner's keystore configuration, etc.... Perhaps these could be configured using TestNG parameters as well. I welcome any additional suggestions/criticisms of my suggestions. Once I've compiled them I will put them in JIRA. Joel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
