tractIntegrationTestSuite 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
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
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
