This rainy weekend, I was inspired by a question from hani about testing servlets. As a result I’ve added a module to Jetty to simply test servlets with an embedded server configured by the ServletTester class. The HTTP requests and responses for testing can be generated and parsed with the
An example of a test harness that uses these classes is ServletTest.

Setting up the tester

The ServletTester can configure a single context. Servlets and Filters may be added to the context by class name or class instance. Context attributes, a resource base or a classloader may optionally be set. eg.

ServletTester tester=new ServletTester();
tester.addServlet("come.acme.TestFilter", "/*");
tester.addServlet(TestServlet.class, "/servlet/*");
tester.addServlet(HelloServlet.class, "/hello");
tester.addServlet("org.mortbay.jetty.servlet.DefaultServlet", "/");

Raw HTTP requests and responses.

The ServletTester takes a string containing requests and
returns a string containing the corresponding responses (eventually byte arrays will be supported for testing character encoding and binary content). More than one request can be pipelined and multiple responses will be returned if persistent connection conditions are met. eg.

String requests=
"GET /context/servlet/info?query=foo HTTP/1.1rn"+
"Host: testerrn"+
"GET /context/hello HTTP/1.1rn"+
"Host: testerrn"+
String responses = tester.getResponses(requests);
String expected=
"HTTP/1.1 200 OKrn"+
"Content-Type: text/html; charset=iso-8859-1rn"+
"Content-Length: 21rn"+
"<h1>Test Servlet</h1>" +
"HTTP/1.1 200 OKrn"+
"Content-Type: text/html; charset=iso-8859-1rn"+
"Content-Length: 22rn"+
"<h1>Hello Servlet</h1>";

Generated Requests, Parsed Responses

Dealing with raw HTTP can be a bit verbose and difficult to test non protocol aspects. The
class allows for simple generation of requests and parsing of response (it can also parse requests and generate responses). eg.

HttpTester request = new HttpTester();
HttpTester response = new HttpTester();
assertEquals("<h1>Hello Servlet</h1>",response.getContent());

Once setup, the HttpTester instances may be reused and only the parts that change need to be
set for subsequent requests. eg.



This will be in the 6.1.0 release and is currently in 6.1-SNAPSHOT. To use these classes you need the jars for servlet-api, jetty-util, jetty, jetty-servlet-tester.


Anonymous · 02/06/2007 at 04:39

It’s nice to be able to test a servlet but how do you set the servletConfig for the servlet under test?

    Gawraozzora · 04/03/2012 at 10:40

    >Thank you very much for this article. It hpeeld me a great deal after a full day of trying to get JSFUnit running with embedded Tomcat.

Eamonn · 19/12/2007 at 10:36

I am trying to find out the same thing. How to set the ServletConfig/init-params programattically in Jetty. Anyone solved this one?

Anonymous · 04/03/2008 at 15:18

I have servlets which use session data to determine their output and behaviour.  Is there any way to set this up using ServletTester?

Stephen · 06/10/2009 at 17:09

If you want to set init parameters for your tests you have to use the ServletHandler class:

ServletTester tester = new ServletTester();
ServletHandler sh = tester.addServlet("ch.primecommerce.SomeServlet", "/*");
sh.setInitParameter("name", "value");


Caoilte O'Connor · 01/03/2011 at 15:36

Five years later this blog entry is still very useful. One problem I had, though, was with the comment advice on setting init-params. I had to do the following instead,

Field contextField = ServletTester.class.getDeclaredField("_context");
Context context = (Context)contextField.get(tester);
context.getInitParams().put("param", "value");

URL · 30/06/2012 at 21:47

… [Trackback]…
[…] Read More: […]…

Comments are closed.