[Jersey] Re: Test Coverage for REST API integration-level tests

From: Behrooz Nobakht <>
Date: Mon, 22 Dec 2014 20:36:37 +0100

Hi Jakub,

Thanks for your reply.

Jersey test framework is indeed a useful base to build tests upon in the
level of integration.
However, since we did not have integration tests on top of Jersey test
framework on Jersey 1.x,
we just started to have a test module that tests our migration end to end.
I agree that building tests on top of Jersey test framework can help,
yet I think we will still miss the granular visibility of how much test
coverage we have
for the REST endpoints that are under test.

This is thinking out loud, but I was thinking of using the WADL feature, and
then come up with a comparison/instrumentation in the end of the test life
such that it shows how much of all REST endpoints defined in the WADL were
by the tests. If I get to implement this, I will share the results as it
may be useful or
even considered a contribution.


On Mon, Dec 22, 2014 at 11:50 AM, Jakub Podlesak <>

> Hi Behrooz,
> There is no Jersey migration automation tool that i would be aware of.
> Please see
> for information on how to migrate from Jersey 1.x specific APIs to Jersey
> 2.0.
> Other parts of the doc describe upgrading within Jersey 2.x version space.
> If you are testing your server side already, you should be able to re-use
> these
> tests for the migrated application. Even Jersey 1.x test framework [1]
> based tests
> should be possible to use for migrated application testing. If you are
> using
> ExternalTestContainerFactory then no big changes are needed,
> otherwise you will need to start/stop tested application and the tests
> separately.
> I can provide more information as requested,
> HTH,
> ~Jakub
> [1]
> On 22 Dec 2014, at 09:32, Behrooz Nobakht <> wrote:
> Hi,
> During migrating from Jersey 1.x to Jersey 2.x, we came to an interesting
> question that could help us
> manage the migration in a more efficient way.
> For a set of integration-level tests for a Jersey application (1.x or 2.x),
> is there a tool/plugin/technique that is recommended to use to help
> understand the coverage
> for the REST API that is used from the server?
> The motivation to have such a tool is that it helps to create a base
> before migration,
> do the migration and then use it as one of the validators of a successful
> migration.
> Such coverage understanding can give us a confidence level of how much of
> the
> migrated REST API function as before.
> Thanks in advance,
> Behrooz

-- Behrooz Nobakht