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-beta-1 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.0.0-beta-1 view tag
Release date	2011-05-13
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-impl-base jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-spi jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-descriptors jar javadoc pom
• org.jboss.shrinkwrap.sip » shrinkwrap-extension-sip-api jar javadoc pom
• org.jboss.shrinkwrap.sip » shrinkwrap-extension-sip-impl jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-vfs3 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-vdf jar javadoc pom

Release notes and resolved issues 7

First release chain in Beta series

Feature Request

• SHRINKWRAP-249 - Support add directory content

Bug

• SHRINKWRAP-276 - Invalid byte stream for ZipExporter

Task

• SHRINKWRAP-172 - Clean up API
• SHRINKWRAP-242 - Get shrinkwrap to work from inside an OSGi framework
• SHRINKWRAP-274 - Set release cycle to 1.0.0-beta-1
• SHRINKWRAP-277 - Extract Container* extensions into their own repos with their own release cycles.
• SHRINKWRAP-280 - Pull out the container integration modules into their own repos

Thanks to the following list of contributors: Andrew Lee Rubinger

Even with the first beta still on the horizon, Arquillian has already begun to transform the enterprise testing landscape, making the formerly untestable testable.

The early influence of the Arquillian project is the result of a legion of community members integrating their diverse skills to flatten the barrier to integration testing. The collaboration across projects and across communities is truly inspiring. It’s safe to say that not only is the Arquillian invasion on, it’s well ahead of its release schedule. And that’s awesome. And the growing community is the reason why.

Noble Ike, the Arquillian prince, and the core project team, would like to recognize the community members that have helped shape Arquillian during each release cycle, either through code contributions, participation or advocacy. For donating their time, effort and patience to make Arquillian a better testing framework for the benefit of the community, we award each of them the title Arquillian Noble.

The Arquillian Nobles page on the project site lists the recipients along with the contributions they made. Contributors are awarded for either a specific release, or for general support of the project. The names of the community members crowned so far are listed here (for reference):

• Pete Muir
• Cheyenne Weaver
• Karel Piwko
• David Allen
• Andy Gibson
• Jason Porter
• Jesper Pedersen
• Jean Deruelle
• Thomas Diesler
• Stale Pedersen
• Nicklas Karlsson
• Ken Gullaksen
• Alejandro Montenegro
• Adrian Cole
• Paul Bakker
• German Escobar
• Michael Schuetz
• Adam Warski
• Markus Eisele
• Cosmin Martinconi
• John Ament
• Stuart Douglas
• Jordan Ganoff
• Lincoln Baxter III
• Mike Brock

Community members may be crowned multiple times. Once a contributor becomes a team member, subsequent contributions are not listed here (team members are noble by default).

In addition to being listed on the Arquillian Nobles page, we are working to get a crown added to each recipient’s JBoss Community profile so that it is globally visible. We’ll announce when that’s available.

The more container adapters and extensions we create, the more power we put in the hands of the developer, and the better enterprise software will become. Feature transparency FTW!

Thanks to all the Arquillian Nobles, present and future, for making Arquillian awesome and for simplifying testing to child’s play!

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

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

What is ShrinkWrap Descriptors?

The Shrinkwrap Descriptor project provides an uniformed fluent API for creating and modifying Java EE deployment descriptors on the fly. Starting from the very early JEE 1.3 to the brand new Java EE 7 version, the descriptor project includes almost all official deployment descriptors. Several vendor specific deployment descriptors, mostly JBoss related, are covered as well.

Release details

Component	ShrinkWrap Descriptors
Version	0.1.7 view tag
Release date	2011-05-02
Released by	Andrew Lee Rubinger
Compiled against	JUnit – 4.8.1

Published artifacts org.jboss.shrinkwrap.descriptors

• org.jboss.shrinkwrap.descriptors » shrinkwrap-descriptors-api jar javadoc pom
• org.jboss.shrinkwrap.descriptors » shrinkwrap-descriptors-impl jar javadoc pom

Release notes and resolved issues 1

Internal Release for JBoss.org Projects

Task

• SHRINKDESC-53 - Create API/Impl Module split

Thanks to the following list of contributors: Lincoln Baxter, III, Andrew Lee Rubinger

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-alpha-13 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.0.0-alpha-13 view tag
Release date	2011-04-27
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-impl-base jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-spi jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-descriptors jar javadoc pom
• org.jboss.shrinkwrap.sip » shrinkwrap-extension-sip-api jar javadoc pom
• org.jboss.shrinkwrap.sip » shrinkwrap-extension-sip-impl jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-glassfish jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-tomcat-6 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-mobicents-sip-servlets-1x jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-jetty-6 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-jetty-7 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-openejb jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-vfs3 jar javadoc pom
• org.jboss.shrinkwrap » shrinkwrap-extension-vdf jar javadoc pom

Release notes and resolved issues 16

Feature Request

• SHRINKWRAP-160 - Add more convenience method to Filters
• SHRINKWRAP-179 - Container.setXX methods should support the new Package construct
• SHRINKWRAP-230 - Create a ShrinkWrap Descriptors extension module
• SHRINKWRAP-235 - Add writeTo methods to Archive
• SHRINKWRAP-256 - addDirectoryOfResourcesRecursively(File dir) would be nice
• SHRINKWRAP-264 - DescriptorAsset should be a NamedAsset

Bug

• SHRINKWRAP-187 - Existing folders will silently be overwritten by files
• SHRINKWRAP-244 - When calling JavaArchiveImpl.addClass(String, ClassLoader) the TCCL gets used instead
• SHRINKWRAP-246 - Shrinkwrap does not work in a modular environment
• SHRINKWRAP-258 - StrictFilter should be moved to maven-api module
• SHRINKWRAP-259 - ShrinkWrap.create(ZipImporter.class) Results in Error
• SHRINKWRAP-269 - Shrinkwrap is hanging in JdkZipExporterDelegate

Task

• SHRINKWRAP-195 - ZipExporterTestCase.testExportArchiveWithOnlyDirectories contains no assertions
• SHRINKWRAP-262 - Unify Aggregator and Build Parent
• SHRINKWRAP-263 - API rename addDirectory to addAsDirectory
• SHRINKWRAP-272 - Remove @Deprecated ZipExporter.exportZip

Thanks to the following list of contributors: Davide D'alto, Tommy Tynjä, Andrew Lee Rubinger, Ivan Pazmino, Samuel Santos, Karel Piwko, Carlo De Wolf

If you think doing integration testing is significantly slower, complex or just plain harder than unit testing, think again. In this video, Aslak shows how quickly you can go from an empty directory (0mph) to a project that runs a CDI test inside a managed JBoss AS 7 container (60mph) in under a minute using the Arquillian plugin for JBoss Forge.

Notice that the test cold boots JBoss AS 7, deploys the tests and runs it in-container, then undeploys and shuts down the server in < 5 seconds. (It runs even faster when you take away the Maven cycle).

A quote by Brian Leathem is suitable for quoting here:

With tools like Arquillian, Shrinkwrap, [and] in-memory databases, [we] are busting through the old barriers of terms like unit and integration tests. Perhaps we need a new term for them: “real tests” or “useful tests” are two possibilities that come to mind.

Don’t mock. Test for real.