Isn't Jetty often used for this kind of tests ? It starts very quickly and can be manipulated programmatically. And if I'm not mistaken the last version of Glassfish allows containers to be created individually for testing. That's very useful to test EJB.
On Fri, Nov 12, 2010 at 12:13, Dominic Mitchell <[email protected]>wrote: > On Thu, Nov 11, 2010 at 7:05 PM, Alexey Zinger <[email protected]>wrote: > >> We're looking at Hudson for a continuous integration solution to run a >> test suite against our Tomcat-hosted web app. As I learn about Hudson, it >> seems like a nice enough package, but it seems like it lacks any way of >> either running tests within the app server itself. I'm hearing about people >> setting up Hudson as a build environment and then make it execute tests that >> invoke an HTTP client that calls the back-end and then assert on results >> (this fits nicely into an AJAXy JSON-driven or similar back-end). There are >> some obvious limitations with this approach, but advantages as well. Are >> there other (better) ways of going about this? Any firsthand experiences? >> > > How difficult is it to bring up an instance of tomcat specifically to run > the integration tests? Could you run your app in jetty instead, which might > be easier to bring up as part of a test? > > -Dom > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
