3 Replies Latest reply on May 6, 2012 3:02 PM by dan.j.allen

Jersey descriptors in test package and REST testing

dan.j.allen May 5, 2012 1:42 PM

From the article Writing lightweight REST integration tests with the Jersey Test Framework, I noticed that Jersey has a webapp descriptor builder in the test package. This is obviously an opportunity to show where ShrinkWrap descriptors can be generally applicable.

WebAppDescriptor.Builder()
    .initParam(WebComponent.RESOURCE_CONFIG_CLASS, ClassNamesResourceConfig.class.getName())
    .initParam(ClassNamesResourceConfig.PROPERTY_CLASSNAMES,
        TodoResource.class.getName() + ";" +
        MockTodoServiceProvider.class.getName() + ";" +
        NotFoundMapper.class.getName()).build();

Here's the JavaDoc for WebAppDescriptor.

This article also reminds us that the Arquillian REST extension prototype is probably worth converting to an official module at this point. I'll follow-up on that in a thread in the Arquillian dev forums.

1. Re: Jersey descriptors in test package and REST testing

dan.j.allen May 5, 2012 2:09 PM (in response to dan.j.allen)

Here's the post on the Arquillian forums about the REST extension: https://community.jboss.org/thread/199281
Actions
2. Re: Jersey descriptors in test package and REST testing

alrubinger May 5, 2012 3:04 PM (in response to dan.j.allen)

Any particular action item for SWD in mind now?

S,
ALR
Actions
3. Re: Jersey descriptors in test package and REST testing

dan.j.allen May 6, 2012 3:02 PM (in response to alrubinger)

Mostly, it was just a heads up, perhaps as motivation to touch base with the Jersey team to see if ShrinkWrap Descriptors might be something they'd be interested in using and advocating.

More specifically, the action item is to write a follow-up blog that demonstrates how the Arquillian REST extension (just setup) and ShrinkWrap Descriptors can be used to simplify this example further. I find these types of blogs to be very useful because they help people understand what where aiming to achieve (i.e., we are revelant to you the reader) and they also paint a picture of how much simpler (and portable) the test can be.

...so, I would start by creating a sample project (either locally or in a samples repo) that we can polish up in preparation for a blog. We've gotten a lot of feedback that developers need to see more of what this platform can do, so these focused blog entries (call it a series) can really help with that education.
Actions

Go to original post