Multi-deployment Test Cases

[meetoblivion]

Hi All

So I wanted to start discussing the idea of multi-deployment test cases.  Right now Arquillian supports multiple deployments via distinct methods.  I recently worked on a test structure that was comprised of 8 deployments in total.  7 of them were dependency deployments and the 8th one being the top most archive that represented our UI layer.  Our project is meant to be distributed, currently deploying standalone JBoss JAR modules, lowest level being our model layer and some utilities/constants.  The higher levels being EJB layers and controllers.  I found it kind of odd with the number of

Would it be possible to support returning an Archive[] or Collection<Archive> in these methods when their order is all relative ( can be ordered based on the entries in the collection/array )?  Something like this:

@Deployment(testable=false,order=1)

public static JavaArchive[] createTestArchive() {

          return {ShrinkWrap.create(JavaArchive.class, "test1.jar")..,

                    ShrinkWrap.create(JavaArchive.class, "test2.jar")..,

                    ShrinkWrap.create(JavaArchive.class, "test3.jar")..};

}

@Deployment(order=2)

public static JavaArchive createTestArchive() {

          return ShrinkWrap.create(JavaArchive.class, "test4.jar")..;

}

One issue is that the name has to be specified with multiple deployments - can the name be derived by archive.getName() ?

[aslak]

John Ament wrote:

@Deployment(testable=false,order=1)

public static JavaArchive[] createTestArchive() {

          return {ShrinkWrap.create(JavaArchive.class, "test1.jar")..,

                    ShrinkWrap.create(JavaArchive.class, "test2.jar")..,

                    ShrinkWrap.create(JavaArchive.class, "test3.jar")..};

}

@Deployment(order=2)

public static JavaArchive createTestArchive() {

          return ShrinkWrap.create(JavaArchive.class, "test4.jar")..;

}

One issue is that the name has to be specified with multiple deployments - can the name be derived by archive.getName() ?

It could work if all archive.getName() is unique. Deployment.name is used to match with @OperatesOnDeployment. In a clustered setup you would have two archives with the same name targets for two different containers.

Look at the DeploymentScenarioGenerator SPI:

https://github.com/arquillian/arquillian-core/blob/master/container/test-spi/src/main/java/org/jboss/arquillian/container/test/spi/client/deployment/DeploymentScenarioGenerator.java

The AnnotationDeploymentScenarioGenerator is the default impl:

https://github.com/arquillian/arquillian-core/blob/master/container/test-impl-base/src/main/java/org/jboss/arquillian/container/test/impl/client/deployment/AnnotationDeploymentScenarioGenerator.java