Arquillian Blog

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

The Arquillian team is proud to announce the 2.0.0.CR1 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	2.0.0.CR1 view tag
Release date	2013-03-13
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

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.0.CR6 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.CR6 view tag
Release date	2013-03-08
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 3

Support for Weld 2.0

Feature Request

• ARQ-1302 - Support Weld 2.x

Bug

• ARQ-841 - Should not scan for classes in Archive if it contains no beans.xml

Thanks to the following list of contributors: Aslak Knutsen, Matt Benson

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

Arquillian Persistence Extension is back on the release train and the future plan is stronger than ever. The Alpha6 release brings a lot of improvements and fixes thanks to invaluable feedback from the community.

Big thanks go to Marco Cella, Matti Linnanvuori, Bernard Łabno, Tiago Wanke Marques, Karsten Ohme, Vineet Reynolds, Cyrill Ruettimann, Bryan Saunders, Anton Shaykin, Nicolas-Xavier Vanderlinden and Noah White for their feedback which led us to fix some minor annoyances and shortcomings of APE. We are proud of the vibrant and active community around Arquillian!

Some of the highlights in this release

Transaction support has been replaced with Transaction Extension. By default the JTA implementation is included. The only thing you will need to change in your tests is the import sttement for the @Transactional annotation. From now on it’s under org.jboss.arquillian.transaction.api.annotation.

Support for row ordering when comparing datasets. When using Generated ID’s for instance, such as UUID’s, the rows need to be sorted in order for the DbUnit comparison to pass. If they are not ordered, then the assertion is unreliable.

Improved error reporting, including rows comparision and misconfigured entries.

DTD support for flat XML data sets (DBUnit feature).

Proper support for multiple line SQL scripts with comments (ANSI SQL compliant)

We’ve also extended our test suite by adding Apache Derby to our continuous integration pipeline.

Important change: We re-groupped configuration entries arquillian.xml giving them more qualifiers:
persistence – for all basic settings
persistence-dbunit – for DBUnit specific configuration
persistence-script – for SQL related things
Please refer to our confluence documentation for detailed description.

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 Persistence Extension
Version	1.0.0.Alpha6 view tag
Release date	2013-03-07
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.0.3.Final Arquillian Transaction Extension – 1.0.0.Alpha3

Published artifacts org.jboss.arquillian.extension

• org.jboss.arquillian.extension » arquillian-persistence-api jar javadoc pom
• org.jboss.arquillian.extension » arquillian-persistence-impl jar javadoc pom
• org.jboss.arquillian.extension » arquillian-persistence-integration-tests jar javadoc pom
• org.jboss.arquillian.extension » arquillian-persistence-integration-tests-testng jar javadoc pom

Release notes and resolved issues 27

Enhancement

• ARQ-1085 - Unify JPA Cache eviction events with APE
• ARQ-1215 - Clean slf4j dependency

Feature Request

• ARQ-1093 - Support for Row Ordering when Comparing Datasets
• ARQ-1149 - Dataset comparision should collect all differences in the rows instead of failing on the first column
• ARQ-1157 - Replace Persistence internal Transaction management with Transaction Extension
• ARQ-1231 - Should observe required object ArquillianDescriptor instead of assuming Lifecycle
• ARQ-1248 - Add Derby to the testing matrix
• ARQ-1333 - Should provide more meaningful diagnostic messages

Bug

• ARQ-1028 - @ShouldMatchDataSet before persist
• ARQ-1081 - DTD not supported by APE
• ARQ-1086 - @CleanuUsingScript with phase NONE
• ARQ-1087 - Wrong dump directory path
• ARQ-1094 - @ShouldMatchDataSet Not Properly Comparing Datasets
• ARQ-1100 - Datetime conversion does not work as expected for YAML data sets
• ARQ-1101 - Exception with nested transaction with MySQL
• ARQ-1127 - Order of scripts and data sets should be preserved when defined on class level
• ARQ-1146 - Single statement which spans multiple lines is not handled properly
• ARQ-1167 - Transactional support from Seam 3 interfere Persistence Extension resulting in ExclusiveTransactionException
• ARQ-1208 - Multiple line statements are not handled properly
• ARQ-1299 - Persistence extension throws NPE with empty table DataSets
• ARQ-1300 - Execute script handler does not properly ignore /* */ and {} ANSI compliant SQL comments

Task

• ARQ-1342 - Clean up POM
• ARQ-1343 - Schema creation scripts should be repeatable

Sub-task

• ARQ-1158 - Extract JTA from APE and replace with Transaction Extension dependency
• ARQ-1334 - Should inform if table defined for exclusion is not defined in the schema
• ARQ-1335 - Should inform when non-defined configuration key encountered in arquillian.xml

Thanks to the following list of contributors: Bartosz Majsak, Jakub Narloch, Aslak Knutsen, Vineet Reynolds, Artur Dryomov

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

The Arquillian team is proud to announce the 1.1.2 release of the ShrinkWrap component!

What is ShrinkWrap?

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	ShrinkWrap
Version	1.1.2 view tag
Release date	2013-03-07
Released by	Andrew Lee Rubinger
Compiled against	JUnit – 4.8.2

Published artifacts org.jboss.shrinkwrap

• org.jboss.shrinkwrap » shrinkwrap-api jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-api-nio2 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-bom pom
• org.jboss.shrinkwrap » shrinkwrap-depchain pom
• org.jboss.shrinkwrap » shrinkwrap-depchain-java7 pom
• org.jboss.shrinkwrap » shrinkwrap-impl-base jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-impl-nio2 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-spi jar javadoc pom

Release notes and resolved issues 2

Bug

• SHRINKWRAP-441 - FileStoreTestCase failure
• SHRINKWRAP-444 - Deploy fail on ZipException("error in opening zip file") when ShrinkWrap.createFromZipFile is used

Thanks to the following list of contributors: Andrew Lee Rubinger, Michal Matloka

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.Alpha1 release of the Arquillian GWT Testing extension component!

This is the first release of the Arquillian GWT extension which aims to bring true integration testing to GWT.

Highlighted Features

Run GWT integration tests in Arquillian containers

This means that GWT integration tests can break free and execute in the actual runtime container instead of being tied to GWT’s embedded Jetty server.

Combining client-side and in-container tests

It is possible to combine GWT client-side and standard in-container tests in the same test class. This allows to test features without having to worry about the client-server bridge and should pave the way for future support of Arquillian Warp and Drone in GWT integration tests.

Getting Started

To start using the Arquillian GWT extension just add the following dependency to your project:

<dependency>
    <groupId>org.jboss.arquillian.extension</groupId>
    <artifactId>arquillian-gwt</artifactId>
    <version>1.0.0.Alpha1</version>
</dependency>

Writing Arquillian GWT tests

To run a test method as a GWT integration test either annotate the test class or test method with @RunAsGwtClient and specifiy the GWT module. If you annotate the test class all test methods in that class will run as GWT integration tests.

@RunWith(Arquillian.class)
public class MyTestClass {

  @Test 
  @RunAsGwtClient(moduleName = "org.myapp.MyGwtModule")
  public void myGwtTest() {

  }
}

To help packaging your app for the test deployment Arquillian GWT provides a simple utility called GwtArchive. The next version of Arquillian GWT will automatically enhance the used WebArchive. So, you won’t need to use this utility in the future. Here’s a complete example:

@RunWith(Arquillian.class)
public class GreeterRpcTest extends ArquillianGwtTestCase {

  @Deployment
  public static WebArchive createDeployment() {
    return GwtArchive.get()
      .addClass(Greeter.class)
      .addClass(GreetingService.class)
      .addClass(GreetingServiceImpl.class);
  }

  @Test
  @RunAsGwtClient(moduleName = "org.myapp.MyGwtModule")
  public void testGreetingService() {
    GreetingServiceAsync greetingService = GWT.create(GreetingService.class);
    greetingService.greetServer("Hello!", new AsyncCallback<String>() {
      @Override
      public void onFailure(Throwable caught) {
        Assert.fail("Request failure: " + caught.getMessage());
      }

      @Override
      public void onSuccess(String result) {
        assertEquals("Received invalid response from Server", "Welcome!", result);
        finishTest();
      }
    });
    delayTestFinish(5000);
  }
}

Note that you will only need to extend ArquillianGwtTestCase if you want to inherit GWT’s asynchronous testing methods (finishTest and delayTestFinish).

We look forward to your feedback on 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 GWT Testing extension
Version	1.0.0.Alpha1 view tag
Release date	2013-02-23
Released by	Christian Sadilek
Compiled against	Arquillian Core – 1.0.2.Final

Published artifacts org.jboss.arquillian.extension

• org.jboss.arquillian.extension » arquillian-gwt jar javadoc pom

Release notes and resolved issues 1

Initial prototype release

Thanks to the following list of contributors: Christian Sadilek, Karel Piwko, Aslak Knutsen