Thinking inside a bigger box - Latest Comments in In-process Web Integration Tests with Jetty and JWebUnit

Re: In-process Web Integration Tests with Jetty and JWebUnit

Johannes Brodwall — Tue, 11 Dec 2012 16:09:33 -0000

Thank you for good feedback.

Re: In-process Web Integration Tests with Jetty and JWebUnit

Tre — Tue, 11 Dec 2012 15:24:46 -0000

I do speak test, and that rocks. I speak maven too, so I'm usually starting jetty with maven for integration testing with the failsafe plugin. This looks fast. Thanks man.

Re: In-process Web Integration Tests with Jetty and JWebUnit

Johannes Brodwall — Mon, 02 Mar 2009 18:33:47 -0000

Thanks for your comment. XSD validation would indeed find some of the defects (like invalid syntax in JSPs), but leave others behind (like the wrong spelling of a bean property name).

But more importantly: Discovering bugs is just one reasons to write tests. There are others, and more important ones.

Re: In-process Web Integration Tests with Jetty and JWebUnit

Web Development — Mon, 02 Mar 2009 07:55:19 -0000

i guess you are using an IDE which doesn't provide proper XSD validation

Re: In-process Web Integration Tests with Jetty and JWebUnit

Kristoffer — Wed, 03 Jan 2007 10:04:51 -0000

One thing worth mentioning (at least for IntelliJ users) is that if you implement tests like Johannes describes in the blog and put them into a sub-module in a multi-module Maven2 project, you will have to explicitly specify the working directory for that module when running the integration test(s). If not you will get FileNotFoundExceptions followed by HTTP 503s for whatever resource you try to hit afterwards.

Re: In-process Web Integration Tests with Jetty and JWebUnit

Kristoffer — Tue, 02 Jan 2007 10:09:03 -0000

I can't get the example up and running from within my favourite IDE(A) after generating the project files with mvn idea:idea because web.xml is not conformant to the Servlet 2.4 specification.

Ok, so I know this is a bit childish :) but I guess you've been using some other IDE of which doesn't provide proper XSD validation(?).

Anyhow, the following fragment (slightly revised) is valid:

<servlet-mapping>
<servlet-name>my</servlet-name>
<url-pattern>/my/*</url-pattern>
</servlet-mapping>