As you can see, Arquillian provides a lot of flexibility in your testing setup. This gives you the ability to test your code as thoroughly as possible in an automated fashion while still having it behave as it would within your deployment structure.
In the next few chapters, I will be exploring more Arquillian extensions, where test cases will range from functional scenarios and browser testing via Selenium to invoking web services on the client side; as well as looking at how to integrate DBUnit with your tests; testing older Seam2 applications as well as Persistence and Transactions to name a few. The next chapter will discuss more general Arquillian extensions such as Persistence, Spock, and JaCoCo.