Servlet unit test

问题:

Currently I'm using TestNG framework for testing application business logic, i added some Servlet classes recently.

How do I unit test these Servlet classes in TestNg framework?

回答1:

Follow skaffman's advice if possible. If not, or if you want to test the behaviour of the servlets as front-end controllers, rather than the business logic inside them, you can use:

• HtmlUnit
• Selenium
• Cactus (but I don't know how whether it supports TestNG already)

回答2:

One of the easiest ways is ServletTester from Jetty. Everything is done within embedded Jetty automatically, so there is no port opened during the testing! If you use Maven than the following artifact is required to enable this method:

<dependency>
  <groupId>org.mortbay.jetty</groupId>
  <artifactId>jetty-servlet-tester</artifactId>
  <version>6.1.16</version>
  <scope>test</scope>
</dependency>

Example:

Prepare ServletTester

ServletTester tester=new ServletTester(); 
tester.addServlet(HelloServlet.class, "/hello"); 
tester.start();

Create HTTP request

HttpTester request = new HttpTester(); 
request.setMethod("GET");
request.setHeader("Host","tester"); 
request.setURI("/hello");
request.setVersion("HTTP/1.0");

Call servlet and retrieve response:

HttpTester response = new HttpTester();
response.parse(tester.getResponses(request.generate()));

Assert what you want to check on response and it's content:

assertEquals(200,response.getStatus()); 
assertEquals("Hello Servlet",response.getContent());

回答3:

I suggest that you move all of the business logic out of the servlet classes, into your own classes which you can test. That leaves the servlets just as glue between your business logic and the container, with nothing in them worth testing.

The API classes such as HttpServletRequest, ServletConfig, etc, are prime targets for using a mocking framework of your choice (JMock, Mockito, etc), since they're all interfaces.