September 3, 2009
(I originally planned this to be a single article, but because of the scope decided to split it into two parts. Read the first part for the the basics of using Sun’s
HttpServer to conduct functional HTTP testing. Here we revisit our functional test and rewrite it using JUnit 4.7’s new Interceptors feature.)
Recall that I thought my initial solution seemed inelegant. It was verbose, with some start up and shutdown code that would have to be repeated for each test, and which I felt cluttered the actual test code.
It was also tedious, in the sense that the raw
HttpExchange API required us to do quite a few things manually, and unintuitively (such as having to compute and write out the length of our response before the response itself).
In this post, we’ll explore how to use the new Interceptors feature ‘quietly’ released with JUnit 4.7 to write reusable, portable pre and post-test behaviour. I’ll also exhibit a convenient
HttpHandler implementation that simplifies some of the effort required in responding to HTTP requests.
September 2, 2009
(I originally planned this to be a single article, but because of the scope decided to split it into two parts. This first part explores the basics of using Sun’s
HttpServer to conduct functional HTTP testing. Part 2 revisits the following test using JUnit 4.7’s new interceptors (rules) feature and demonstrates a simpler HTTP handler.)
At work, we recently had the need to perform functional testing of a custom client that used HTTP as a transport. This isn’t strictly unit testing since we’re conducting actual HTTP over a socket & port instead of stubbing out or mocking the server, but in this case that was the only real way to test the client.
I could’ve fired up a standalone Web server and used that, but decided against it for a couple of reasons.
First, I wanted to have the server respond in a specific way to a particular client request. For example, if the request was for
GET /1234.xml I might want to respond with an
HTTP 200 and an XML response body. Another request for
GET /0.xml might return an
HTTP 404 instead.
To do that using, say, a Servlet container would mean writing multiple Servlets (mapped to various request URI) or a ‘rich’ Servlet with additional complexity. I didn’t want to have to write tests to test my test scaffolding!
Secondly, a standalone server would have to be started and stopped outside of our standard compile/test/package process (using Maven). Other people wouldn’t be able to run the tests successfully without having the test server up as well.
Clearly, the best way to go was to use an embedded HTTP server, which would allow us to provide specific responses tailored for each unit test.
As luck would have it, it turns out that Sun’s Java 6 implementation comes with a lightweight HTTP server API built in. Read on as I demonstrate the basic use of Sun’s HTTP server classes to write a functional test.
David Saff wrote in on Introducing MagicTest, asking why not just instantiate the variable in-line (
private Foo foo = new Foo();).
Which brings me to the real reason for coming up with
A code sample is worth a thousand words. Suppose we have a Spring JPA data access object:
WidgetDao needs a JPA
EntityManager provided to it at construction time. Normally, to write a unit test for
WidgetDao we’d have to create our mock objects and setup our test scaffolding manually.
ActiveTest, however, all we need to write is:
I’m lazy like that.
Read the rest of this entry »
May 28, 2009
If you’ve written enough JUnit 4 tests, then you should be familiar with code that looks like:
Now, how often have you wished it were possible to simply go straight to
@Test, do not pass
setUp(), do not have to
So I came up with
MagicTest, a parameterized base class for JUnit 4 tests that’ll let us do just that. Read the rest of this entry »