[arquillian-issues] [JBoss JIRA] (ARQ-74) Base test deployment on project in which test is run

[Dan Allen (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689303#comment-12689303 ] 

Dan Allen commented on ARQ-74:
------------------------------

This topic recently came up in the Testing SIG in the thread "Testing deployment of pre-built .war to various web servers" - https://community.jboss.org/message/730868#730868

The current state of affairs / workaround, as Marek pointed out, is

{code:java}
ShrinkWrap.create(ZipImporter.class, "foo.war").importFrom(new File("target/foo.war"))
{code}

The caveat is that you have to make sure your test runs in the integration-test maven phase, that is after "package".

That workaround, however, is at odds with the goal of the Arquillian project, which is to skip the build when testing.

In that thread, I proposed an annotation that would build a deployment (using ShrinkWrap Resolvers) based on the current project's artifact. Here's how it would be used:

{code:java}
@RunWith(Arquillian.class)
@DeployProjectArtifact
public class MyFunctionalTest {
    @ArquillianResource
    private URL url;
 
    @Test
    public void shouldBehaveSomeWay() {
       // make a request to the url
    }
}
{code}

Of course, in this case, a @Deployment method would not be required (which is possible through an extension).

I had hacked up an extension prototype a while back that implements this idea, though it uses the older ShrinkWrap Resolver...which would be replaced by the new ShrinkWrap Resolver APIs, which are being discussed in this forum thread: https://community.jboss.org/message/731735

https://gist.github.com/2477705

According to Karel:

{quote}
Now we have a ShrinkWrap Resolver Maven Plugin, @DeployProjectArtifact might work without specifying path to the pom, active profiles, etc. However, IDE support for the plugin is still an open question here.

This is an actual show-stopper for the moment https://issues.jboss.org/browse/SHRINKRES-18. If implemented, creating an Arquillian extension with @DeployProjectArtifact annotation would be an easy task.
{quote}

Karel also suggested that this annotation should be a part of ShrinkWrap Maven Resolver. Once on classpath, you can do Maven magic for deployments.

Alternate names for the annotation are as follows:

* @DeployBuildOutput
* @DeployProjectArchive

I prefer either "project artifact" or "project archive" since it's not just the output, but rather the package that the build is creating.
                
> Base test deployment on project in which test is run
> ----------------------------------------------------
>
>                 Key: ARQ-74
>                 URL: https://issues.jboss.org/browse/ARQ-74
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Packaging Enricher SPI
>            Reporter: Pete Muir
>             Fix For: 1.1.0.Beta1
>
>
> A common testing scenario will be to deploy the artifact generated by the current project, and run tests against it.
> For example, say my project was building a war, I want to be able to deploy that war, inserting the test case and any beans into the deployment, and have my tests run.
> In this case the deep control of the classpath through shrinkwrap is getting in the way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira