In this chapter, we have gone through one critical part of enterprise systems: integration testing. Historically, one main downside of Java EE is its testability, but Arquillian has really solved this issue to a great extent.

Used as an extension of the JUnit framework, Arquillian excels in checking the integration layer that exposes the business logic in an enterprise Java application.

Arquillian hooks into your testing framework's life cycle and starts reacting to events to manage the container (start/stop). It also bundles the test class into a deployable archive with dependent classes and resources.

In the next chapter, we will discuss developing applications using JBoss Messaging Provider (HornetQ) by introducing examples with message-driven beans.