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)

Summary


While not covering every single framework around, this chapter was meant to give a little bit of history as well as a few highlights about testing frameworks. This history is meant to give you a background on where Arquillian came from and the need to create a stable and reusable testing infrastructure that can be extended to support many different test cases.

As shown here, your application can be in many shapes or sizes but still use Arquillian to test your services or components. As we will begin to explore, the range of what Arquillian can work with is quite wide and grows more as contributors help add functionality. An important point to raise is that you must remember to use the right tool in your arsenal. Arquillian will help with your deployment and automated testing, but if you just want to use automated tests you should consider your strategy overall.

A part of what makes Arquillian powerful is that it allows your objects to be integrated with your container. Your test case...