Arquillian Blog

Since we wrote this post we didn't laze around. Check our latest announcement.

The Arquillian team is proud to announce the 1.0.0.CR7 release of the Arquillian Core component!

Some of the highlights in this release

• Configure Arquillian using properties – Adding -Dproperty.name=value to the command line can now add or override values defined in arquillian.xml.

arq.container.[qualifier].mode
arq.container.[qualifier].default
arq.container.[qualifier].configuration.[property_name]
arq.container.[qualifier].protocol.[type].[property_name]

arq.group.[qualifier].default
arq.group.[qualifier].container.[qualifier].configuration.[property_name]
arq.group.[qualifier].container.[qualifier].protocol.[type].[property_name]

arq.extension.[qualifier].[property_name]

arq.defaultprotocol.[type]
arq.defaultprotocol.[type].[property_name]

arq.engine.[property_name]

Example:

-Darq.container.production.configuration.jbossHome=/opt/jbossas/

You can add these in a properties file as well. Default Arquillian will look for a file called arquillian.properties on classpath or on disk, same with arquillian.xml. If you want to configure a different filename, you can use either -Darquillian.properties=name or -Darquillian.xml=name

Since the xml file is read first, the properties will add / override the xml values. In the case where you have a container defined as default in xml, but want to override the default in properties, you can add -Darquillian.launch to specify which container/group configuration to use.

• @OperateOnDeployment on @ArquillianResource injection points

URL, InitialContext and Context on the client side can be qualified with the @OperateOnDeployment annotation.

@Deployment(name = "X")
public WebArchive appX() { ... }

@Deployment(name = "Y")
public WebArchive appX() { ... }

@Test @OperateOnDeployment("X")
public void shouldBeInjected(
      @ArquillianResource URL appXUrl,
      @ArquillianResource @OperateOnDeployment("Y") URL appYUrl)
{
  // ...
}

What is Arquillian?

Arquillian is open source software that empowers you to test JVM-based applications more effectively. Created to defend the software galaxy from bugs, Arquillian brings your test to the runtime so you can focus on testing your application's behavior rather than managing the runtime. Using Arquillian, you can develop a comprehensive suite of tests from the convenience of your IDE and run them in any IDE, build tool or continuous integration environment.

Release details

Component	Arquillian Core
Version	1.0.0.CR7 view tag
Release date	2011-12-15
Released by	Aslak Knutsen
Compiled against	ShrinkWrap – 1.0.0-cr-1 ShrinkWrap Descriptors – 1.1.0-beta-1 ShrinkWrap Resolver – 1.0.0-beta-5 JUnit – 4.8.1 TestNG – 5.14.6

Published artifacts org.jboss.arquillian.core

• org.jboss.arquillian.core » arquillian-core-api jar javadoc pom
• org.jboss.arquillian.core » arquillian-core-spi jar javadoc pom
• org.jboss.arquillian.core » arquillian-core-impl-base jar javadoc pom
• org.jboss.arquillian.config » arquillian-config-api jar javadoc pom
• org.jboss.arquillian.config » arquillian-config-spi jar javadoc pom
• org.jboss.arquillian.config » arquillian-config-impl-base jar javadoc pom
• org.jboss.arquillian.test » arquillian-test-api jar javadoc pom
• org.jboss.arquillian.test » arquillian-test-spi jar javadoc pom
• org.jboss.arquillian.test » arquillian-test-impl-base jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-spi jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-impl-base jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-test-api jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-test-spi jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-test-impl-base jar javadoc pom
• org.jboss.arquillian.junit » arquillian-junit-core jar javadoc pom
• org.jboss.arquillian.junit » arquillian-junit-standalone jar javadoc pom
• org.jboss.arquillian.junit » arquillian-junit-container jar javadoc pom
• org.jboss.arquillian.testng » arquillian-testng-core jar javadoc pom
• org.jboss.arquillian.testng » arquillian-testng-standalone jar javadoc pom
• org.jboss.arquillian.testng » arquillian-testng-container jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-cdi jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-ejb jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-resource jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-initialcontext jar javadoc pom
• org.jboss.arquillian.protocol » arquillian-protocol-servlet jar javadoc pom
• org.jboss.arquillian.protocol » arquillian-protocol-jmx jar javadoc pom
• org.jboss.arquillian » arquillian-bom pom

Release notes and resolved issues 8

Feature Request

• ARQ-284 - Configuration options should be loadable from multiple sources
• ARQ-533 - Support Qualifiers on @ArquillianResource in ResourceProvider's SPI
• ARQ-645 - @ArquillianResource @OperatesOnDeployment("foo") URL; for multiple containers
• ARQ-677 - Expose Deployment as part of TestDeployment so SPIs can access more information, e.g. Container
• ARQ-692 - Update to jboss-parent:8 Contains 1.5/1.6 source level IDE issue

Bug

• ARQ-678 - ExceptionProxy - java.lang.NoClassDefFoundError: org/jboss/util/id/SerialVersion
• ARQ-699 - @ArquillianResource Deployer gets injected only for the first test when using manual deployment/container modes

Thanks to the following list of contributors: Aslak Knutsen