[Jersey] Re: Speeding up jersey-test?

From: Srinivas Naresh Bhimisetty <>
Date: Thu, 7 Apr 2011 10:39:21 +0530


  as you observed, the JerseyTest starts and stops the test container before
(@Before) and after (@After) each test method is executed. This sure could
be the cause of the time being taken to execute each test method.

  Probably, changing the JerseyTest implementation to start/stop the test
container only once (using the @BeforeClass, @AfterClass annotations), for
all the test methods defined in a test class should help overcome this.

- Naresh

On Tue, Apr 5, 2011 at 12:18 AM, Gili <> wrote:

> Hi,
> Jersey-test is quite slow. Granted, the unit tests are doing a lot
> (starting
> up a web server, running the test and shutting down the web server) but the
> end-result is that each @Test takes a minimum of a second compared with
> milliseconds used by my other unit tests. I am using the Grizzly web
> container.
> Is there a way to speed up these unit tests? How fast is
> InMemoryTestContainer? I can't use it on my end because it doesn't seem to
> be compatible with Guice but I'm just curious how if it makes a big
> difference.
> Thanks,
> Gili
> --
> View this message in context:
> Sent from the Jersey mailing list archive at