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.1.0.Final release of the Arquillian Drone Extension component!

We’ve introduced new features in 1.1.0.Final while still preserving backwards compatibility with 1.0.0.Final. There’s now a much simpler way to configure Drone, better support for the Opera browser and support for browsers on iOS devices.

Significant changes since 1.0.0.Final

Browser capabilities instead of implementationClass and native capability configuration

Think of any WebDriver capability, such as opera.no_restart or acceptSSLCerts, and you can now specify it directly in arquillian.xml:

arquillian.xml

<extension qualifier=“webdriver”>

    <property name=“browserCapabilities”>opera</property>

    <property name=“opera.no_restart”>true</property>

    <property name=“acceptSSLCerts”>false</property>

</extension>

Support for reusable browsers

Reusable browsers stay connected even if you finish the tests. This will speed up turnaroud when developing the application. Reusable browsers are based on top of remote browsers, so you’ll need Selenium Hub (run selenium-server-standalone-2.25.0.jar) running during your tests. This is how you enable them (remoteAddress is optional, default value listed here):

arquillian.xml

<extension qualifier=“webdriver”>

    <property name=“browserCapabilities”>chrome</property>

    <property name=“remoteReusable”>true</property>

    <property name=“remoteAddress”>http://localhost:4444/wd/hub</property>

</extension>

Better support for the Opera browser

Support for browsers on iOS devices

Deprecated Arquillian Drone system properties configuration

The system properties configuration provided by Arquillian Core is now the preferred way to configure Arquillian Drone. The old style of system properties still work, but using them will produce warnings in the log and will be removed completely in a future version. Now use arq.extension.extensionName.propertyName to override a value from arquillian.xml file

I’d like to thank everybody from the community eagerly adopting new releases, discovering bugs and providing bugfixes. You guys are awesome!

We hope that you’ll enjoy the improvements. We look forward to hear your feedback in the community forums.

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 Drone Extension
Version	1.1.0.Final view tag
Release date	2012-10-24
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.0.2.Final Selenium – 2.25.0

Published artifacts org.jboss.arquillian.extension

• org.jboss.arquillian.extension » arquillian-drone-bom pom
• org.jboss.arquillian.extension » arquillian-drone-selenium-depchain pom
• org.jboss.arquillian.extension » arquillian-drone-webdriver-depchain pom
• org.jboss.arquillian.extension » arquillian-drone-api jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-spi jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-configuration jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-impl jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-selenium-server jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-selenium jar javadoc pom
• org.jboss.arquillian.extension » arquillian-drone-webdriver jar javadoc pom

Release notes and resolved issues 9

Component Upgrade

• ARQ-1170 - Update Selenium to 2.25.0

Enhancement

• ARQ-929 - Drone: Switch useJavaScript to true by default
• ARQ-1165 - Remove ChromeDriver tests exclusions

Feature Request

• ARQ-1164 - Use default Chrome location for tests

Bug

• ARQ-1048 - RemoteWebDriver ignores old configuration properties
• ARQ-1110 - can't create an instance of IPhoneDriver
• ARQ-1113 - Add @Deprecation to ConfigurationMapper.fromSystemConfiguration

Sub-task

• ARQ-1112 - Verify Arquillian Drone can run on JDK 1.5

Thanks to the following list of contributors: Karel Piwko, Aslak Knutsen, Jan Papoušek

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

The Arquillian team is proud to announce the 1.0.3.Final release of the Arquillian OSGi component!

What is Arquillian OSGi?

ShrinkWrap is the simplest way to create archives in Java. Using the fluent and intuitive ShrinkWrap API, developers may assemble JARs, WARs, and EARs to be deployed directly by Arquillian during testing.

Release details

Component	Arquillian OSGi
Modules	Arquillian OSGi :: Container :: JBoss :: Embedded Arquillian OSGi :: Container :: Felix :: Embedded Arquillian OSGi :: Container :: Equinox :: Embedded Arquillian OSGi :: Container :: Karaf :: Managed Arquillian OSGi :: Container :: Karaf :: Remote
Version	1.0.3.Final view tag
Release date	2012-10-23
Released by	Thomas Diesler
Compiled against	Arquillian Core – 1.0.2.Final ShrinkWrap – 1.0.0

Published artifacts org.jboss.arquillian.testenricher

• org.jboss.arquillian.testenricher » arquillian-testenricher-osgi jar javadoc pom
• org.jboss.arquillian.protocol » arquillian-protocol-osgi jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-osgi jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-osgi-embedded jar javadoc pom

Release notes and resolved issues 5

Containers OSGi - Final

Enhancement

• ARQ-468 - Automatically add test super classes for OSGi

Feature Request

• ARQ-1152 - Add support for OSGi types as ArquillianResource
• ARQ-1153 - Add support for multiple bundle deployments per test case
• ARQ-1159 - Add support for Felix/Equinox testing

Task

• ARQ-954 - Remove dependency on jboss-logging in OSGi Bundle

Thanks to the following list of contributors: Thomas Diesler

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

The Arquillian team is proud to announce the 1.0.3.Final release of the Arquillian Core component!

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.3.Final view tag
Release date	2012-10-18
Released by	Aslak Knutsen
Compiled against	ShrinkWrap – 1.0.1 ShrinkWrap Descriptors – 2.0.0-alpha-3 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 3

TestNG Bug fix

Feature Request

• ARQ-1102 - Publish Test Source jars to Nexus

Bug

• ARQ-563 - @ArquillianResource in TestNG based tests causes test body not to be evaluated

Thanks to the following list of contributors: Aslak Knutsen, Lukas Fryc, Kristoffer Richardsson

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.Alpha2 release of the Arquillian Portal Extension component!

The Portal extension for Arquillian brings testing into the world of Portlets!

Some of the highlights in this release

URL injection of portlets by name. @PortalURL now supports defining the names of the portlets that you want rendered on the page of the injected URL. You can either specify a single portlet name, multiple, or leave it empty and it will load all portlets defined within portlets.xml onto the page. Injecting a URL of a portlet page with the MyPortlet portlet present is done by:

@ArquillianResource
@PortalURL("MyPortlet")
URL portletPage;

Annotation for marking portlet tests. @PortalTest now represents a marker on a test class that signifies to Portal extension implementations that a portlet test is being invoked. This enables for augmenting the test deployment with whatever information is needed for particular portlet containers to enable a portlet to be tested. It has the added benefit of decoupling a test needing to inject a @PortalURL if the tests don’t require a URL to the portlet page.

Currently there are two implementations of this extension for use with Pluto and GateIn portal containers.

For examples on how to use these extensions with their respective portal containers, you can take a look at the testsuite of JBoss Portlet Bridge.

We look forward to hearing your feedback about this release in the community forums!

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 Portal Extension
Version	1.0.0.Alpha2 view tag
Release date	2012-10-17
Released by	Ken Finnigan
Compiled against	Arquillian Core – 1.0.2.Final

Published artifacts org.jboss.arquillian.extension

• org.jboss.arquillian.extension » arquillian-portal-api jar javadoc pom
• org.jboss.arquillian.extension » arquillian-portal-spi jar javadoc pom
• org.jboss.arquillian.extension » arquillian-portal-impl jar javadoc pom
• org.jboss.arquillian.extension » arquillian-portal jar javadoc pom

Release notes and resolved issues 6

Enhancement

• ARQ-1117 - Support Portal URL for specific portlet or several on a page

Bug

• ARQ-961 - Error in README for the name of additional URL qualifier

Task

• ARQ-1115 - Introduce Portal depchain
• ARQ-1116 - Change references of portal container to portlet container
• ARQ-1151 - Update Portal Extension to Core 1.0.2.Final

Thanks to the following list of contributors: Ken Finnigan, Thomas Delhoménie

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.CR4 release of the Arquillian Container Weld Root POM component!

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 Container Weld Root POM
Modules	Arquillian Weld Root POM Container Adapter Arquillian Weld Container Adapter
Version	1.0.0.CR4 view tag
Release date	2012-10-17
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.0.2.Final

Published artifacts org.jboss.arquillian.container

• org.jboss.arquillian.container » arquillian-weld-ee-embedded-1.1 jar javadoc pom
• org.jboss.arquillian.container » arquillian-weld-se-embedded-1 jar javadoc pom
• org.jboss.arquillian.container » arquillian-weld-se-embedded-1.1 jar javadoc pom

Release notes and resolved issues 6

Feature Request

• ARQ-1160 - Prepare Weld CR4

Bug

• ARQ-753 - ShrinkWrapClassLoader does not find service provider in WAR
• ARQ-817 - arquillian-weld-container does not build on Maven Default Profile
• ARQ-818 - WebArchiveClassLoader only honors resource requests for Service files
• ARQ-819 - Wrong criteria used for supplying Weld with WebArchiveClassLoader
• ARQ-890 - WeldEEMockContainer does not clean up resources if the deployment fails

Thanks to the following list of contributors: Jozef Hartinger, Aslak Knutsen, Martin Kouba, Andrew Lee Rubinger