I've always been under the impression that the purpose of the TestNG "parameter" paradigm is that it's a hook to help you dynamically configure your tests. And since we're using TestNG...
Not sure what you mean with the whole constructor idea? Surefire's the one instantiating my tests. My custom variation runs one Jetty/Selenium/client instance for all of my test executions. Works just fine (except for the whole HTTPS thing I mentioned). As far as the multiple applications... That's a tricky one... Perhaps just two different flavors of the AbstractIntegrationTestSuite with some shared code? I'd imagine most people don't need the multiple applications and would rather have just one instance of Jetty. -----Original Message----- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Thursday, February 28, 2008 2:39 PM To: Tapestry users Subject: Re: T5.0.11-SNAPSHOT: tapestry-test suggestions I'm thinking that instead of a bunch of unrelated configuration values and constants, perhaps a single object that contains all of them, that can be passed to the constructor. BeforeSuite/AfterSuite: Have to look into this; right now, T5's tests start up a series of different applicaitions to test various odds and ends. Perhaps we could juggle it to just start/stop Jetty and leave Selenium (server and browser app) running the whole time? On Thu, Feb 28, 2008 at 11:30 AM, Joel Wiegman <[EMAIL PROTECTED]> wrote: > 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_wort > h_ > 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] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
