As we've seen, ShrinkWrap has a lot of useful classes for creating and manipulating archives. It also has advanced features for managing your Maven dependencies to add to your test cases dynamically. ShrinkWrap is meant to be fluent. The lead developer of the project designs this with an API-first mentality—does this work well for a developer who may be using it? This is how the DSL approach for ShrinkWrap came to be.
Thank you for reading this book! Hopefully you got as much out of reading it as I did from writing it. My goal was to bring you top to bottom on an introductory level to Arquillian to start writing test cases that may deploy to a container.