real java ee testing with arquillian and shrinkwrap

Real Java EE Testing withReal Java EE Testing with

ArquillianArquillian andand ShrinkWrapShrinkWrap

Dan AllenDan AllenSenior Software EngineerSenior Software EngineerJBoss, by Red HatJBoss, by Red Hat

Don't fake it!

2 Real Java EE Testing: Arquillian and ShrinkWrap | Dan Allen

Who am I?

● Author of Seam in Action, Manning 2008

● Seam Community Liaison

● Weld, Seam & Arquillian project member

● JSR-314 (JSF 2) EG representative

● Open Source advocate

mojavelinux

Agenda

● Testing, what's the problem?

● Integration testing challenges

● A component model for tests

● ShrinkWrap

● Arquillian

● Case study

#testrevolution

Why don't we test?

Common integration testing challenges

● Active mocks to stand in for collaborators

● Configure application to use test data source(s)

● Deal with (lack of) classpath isolation

● Run a build to create/deploy application archive

Test in-container!Test in-container!

Skip the Build!

container

n. manages a runtime environment and provides resources,a component model and a set of services

model for testsmodel for tests

A component

Unit tests vs integration tests

● Fine-grained

● Simple

● Test single API call

● Fast, fast, fast

● Easily run in an IDE

Integration

● Coarse-grained

● Complex

● Test intricate web of calls

● Sloooooooow

● Run in an IDE? How?

Testing bandgap and compounding effort

Unit Tests Integration Tests Functional Tests

Functional complexity

Thought and effort

Testing continuum with Arquillian

Unit Tests Integration Tests Functional Tests

Functional complexity

Thought and effort

In-container approach to integration testing

● Separate container process

● Test deployed as archive

● Test runs in-container

● Results collected remotely

Weighing in-container testing

● Rely on shared memory

● Pass-by-reference

● Don't need remote views

● Managed concurrency

● Lack of isolation

● Environment not “true”

Don't tie your tests to a build!

● Extra, external setup

● Adds time to tests

● Coarse-grained packaging

n. a simple, Apache-licensed Java API for assembling archiveslike JARs, WARs, EARs; developed by the JBoss Community

Benefits of ShrinkWrap

● IDE incremental compilation● Save and re-run● Skip the build!

● Simple API

● Tooling views

● Export and debugging

● Micro-deployments

Fluent archive creation

final JavaArchive archive = ShrinkWrap.create("slsb.jar", JavaArchive.class) .addClasses(Greeter.class, GreeterBean.class);System.out.println(archive.toString(true));

slsb.jar:/com//com/acme//com/acme/app//com/acme/app/ejb3//com/acme/app/ejb3/Greeter.class/com/acme/app/ejb3/GreeterBean.class

Yields output:

Architecture overview

n. a simple, Apache-licensed test harness that abstracts awaycontainer lifecycle and deployment from test logic so developerscan easily develop a broad range of integration tests for theirenterprise Java applications; developed by the JBoss Community

Make integration testing a breeze!

The mission of the Arquillian project is to...

Prove it!

@RunWith(Arquillian.class)public class GreeterTestCase { @Deployment public static JavaArchive createTestArchive() { return ShrinkWrap.create("test.jar", JavaArchive.class) .addClasses(Greeter.class, GreeterBean.class); } @EJB private Greeter greeter; @Test public void shouldBeAbleToInjectEJB() throws Exception { assertEquals("Hello, Earthlings", greeter.greet("Earthlings")); }}

Arquillian guts the plumbing

● Manages lifecycle of container● start/stop● bind/unbind

● Enriches test class (e.g, @Inject, @EJB, @Resource)

● Bundles test archive● code under test● libraries● test class and invoker (in-container run mode only)

● Negotiates deployment of test archive

● Captures test results and failures

Benefits of Arquillian

● Write less (test) code

● As much or as little “integration” as you need

● Looks like a unit test, get fully functioning components

● Simple way to get an instance of component under test

● You don't hesitate when you need a resource

● Same test, multiple containers

● It's the real deal!

Test frameworks

JUnit TestNG>= 4.6 >= 5.10

Test archives

● Built using ShrinkWrap API

● Bundle:● code under test● dependent Libraries● test class and invoker (in-container run mode only)

● Deployed to container before test is executed

● Undeployed after test is executed

Build, what build?

@Deploymentpublic static JavaArchive createTestArchive() { return ShrinkWrap.create("test.jar", JavaArchive.class) .addClasses(Greeter.class, GreeterBean.class);}

Skip the build!

@Deploymentpublic static JavaArchive createTestArchive() { return ShrinkWrap.create("test.jar", JavaArchive.class) .addPackage(TranslateController.class.getPackage()) .addManifestResource( new ByteArrayAsset("<beans/>".getBytes()), ArchivePaths.create("beans.xml"));}

Micro deployments

● Deploy components in isolation

● Test one slice at a time

● Don't need to wait for full application build/startup

● Tune size of integration● Layers by inclusion● No “big bang”

Containers

● Mode

● Capability

Container modes

● Embedded● Same JVM as test runner● Tests executed by native test runner● Lifecycle controlled by Arquillian

● Remote● Separate JVM from test runner● Tests executed over remote protocol● Arquillian likely binds to ports

Container capabilities

● Java EE application server (JBoss AS, GlassFish, etc)

● Servlet container (Tomcat, Jetty)

● Managed bean container (Weld SE, Spring)

● OSGi

● SPI allows you to introduce any other container

Not just for Java EE

public interface DeployableContainer {

void setup(Context context, Configuration configuration);

void start(Context context) throws LifecycleException;

ContainerMethodExecutor deploy(Context context, Archive<?> archive) throws DeploymentException;

void undeploy(Context context, Archive<?> archive) throws DeploymentException;

void stop(Context context) throws LifecycleException;

Test enrichment

● Injection● Fields & method arguments● @Inject, @Resource, @EJB, etc.

● Contexts● Request & Conversation Test method ● Session Test class● Application Test class

● Interceptors & decorators

Test run modes

● In-container● Test bundled in @Deployment archive● Archive deployed to container● Test runs inside container with code under test● Test invokes code under test directly (same JVM)

● Local● @Deployment archive unmodified● Archive deployed to the container● Test runs in original test runner● Test interacts as a remote client (e.g., HTTP client)

In-container testing MDBs: A case study

● Asynchronous● How will client know server is done processing?● Thread.sleep() is prone to transient failures

● No return value● How do we check post-conditions?

● In-container == same JVM● Gives test control● Allows test to inspect contexts

Arquillian is...

● an innovative approach to testing

● a component model for tests

● test infrastructure & plumbing

● a set of container implementations

● a little bit of magic ;)

JBoss Testing Initiative

● Comprehensive testing tool “stack”

● Establish a testing culture in Java EE● #jbosstesting on irc.freenode.net

● Filling voids● ShrinkWrap – Programmatic archive creation● Arquillian – Managed integration testing● Placeebo – Mock Java EE API implementations● JSFUnit – Gray-box JSF testing● Contribute to the unit testing frameworks?

Get Involved!

● Active and open community

● How to contribute:● Ideas on forums or IRC● Feedback on releases – still in alpha!● Enhancements and bug fixes – we love patches!● Documentation● Blogs – share your stories!

● Come meet us:● http://jboss.org/arquillian● #jbosstesting on irc.freenode.net

http://jboss.org/arquillian

Q & AQ & A

Dan AllenDan AllenSenior Software EngineerSenior Software EngineerJBoss, by Red HatJBoss, by Red Hat

http://jboss.org/arquillianhttp://jboss.org/arquillianhttp://jboss.org/shrinkwraphttp://jboss.org/shrinkwrap

real java ee testing with arquillian and shrinkwrap

shrinkwrap dan allen

testing bandgap

testing continuum

testrevolution testing

benefits of arquillian

shrinkwrap dont

container testing proscons

real deal

Technology

2012-10-12 testen mit arquillian

web-anwendungen mit arquillian testen - bed-con.org ·...

testing the enterprise layers, with arquillian

testing javaee applications using arquillian by reza rahman

arquillian: the extendable enterprise test platform

shrinkwrap, clickwrap and beyond contracts – prof. merges...

packing guide - dhl.es · stretch or shrinkwrap to the...

introduction to arquillian framework

marsjug - une nouvelle vision des tests avec arquillian

arquillian in a nutshell

testes em aplicações java ee com arquillian · 2015. 3....

september 2010 - arquillian

developer productivity with forge, java ee 6 and arquillian

integration test with arquillian and jboss as 7

arquillian reference guide

arquillian - yajug - nov. 2012

devoxxfr 2013 - arquillian

extending arquillian graphene

arquillian extensions

tests d'intégration avec arquillian