Book Image

Arquillian Testing Guide

By : John D. Ament
Book Image

Arquillian Testing Guide

By: John D. Ament

Overview of this book

<p>Integration testing sometimes involves writing complex codes. This book introduces you to the capabilities of Arquillian to enable you to write simple code with a broad range of integration tests for java applications. <br /><br />Arquillian Testing Guide serves as an introductory book to writing simple codes for testing java applications. This book will help you to develop richer test cases which can be run automatically while performing rigorous testing of the software. <br /><br />Arquillian Testing Guide introduces you to Arquillians features and capabilities. This book will help you understand the mechanism of creating deployments and test against those deployments. The book begins with basic JUnit test cases beginning with an enterprise test case, which then go on to discuss remote testing. During the course of the book, you will also learn how to mix container and non-container tests into a single test case. By the end of the book, you will have learned how to extend JUnit tests to work with Arquillian and deploy them to a container automatically.</p>
Table of Contents (17 chapters)

Containers and deployments


Containers represent what your application will run on. This is the code that represents what you would typically run on top of the application server. The deployments though are what represent your code as standard Java Archives – JAR, WAR, EAR, RAR—that can be deployed to an application server to run code.

At the start of this, I want to remind you to consult with the Arquillian Reference Guide for the latest container setup. The list of containers can be found at https://docs.jboss.org/author/display/ARQ/Container+adapters.

Deployments

This section is meant to be a brief crash course in using ShrinkWrap to create archives. The ShrinkWrap API is designed via Factory and Builder patterns. There is a utility class – ShrinkWrap – that acts as the entrance for the factory of archives. Calling ShrinkWrap.create(JavaArchive.class); will generate a new Java Archive (representing a JAR file).

Arquillian uses a static method defined in your test case to create the archive...