Hi Behrooz,
There is no Jersey migration automation tool that i would be aware of.
Please see
https://jersey.java.net/documentation/latest/migration.html#mig-1.x <
https://jersey.java.net/documentation/latest/migration.html#mig-1.x>
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]
https://jersey.java.net/documentation/1.18/test-framework.html <
https://jersey.java.net/documentation/1.18/test-framework.html>
> On 22 Dec 2014, at 09:32, Behrooz Nobakht <nobeh5_at_gmail.com> 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
>