跳至主要内容

Book Review: Arquillian Testing Guide




Today I have received my hard copy of the book, Arquillian Testing Guide. Comparing to the resource I had got at the end of last year, much content are improved.
Arquillian is a modern Java EE testing framework, based the well-known JUnit or TestNG, brought by JBoss.org.
In fact, currently Arquillian is beyond Java EE, and not only for Java EE application and Java EE container, such as it also supports Android application test and can run test in Android system(or Android simulator) . Most of my Arquillian experience is based on Java EE.
If you have some experience of JUnit experience before, and eager to find a testing solution for your Java EE application and want to run the test case in container automatically, this book is for you.
With Arquillian, you are free from preparing the test fixture before you write real tests. You can write tests in the nature way, such as using @Inject, @Resource etc in your test case directly as the way in your classes.
Let's have a look at what is included in the book.
Chapter 1 : What is Arquillian is a conceptual introduction to Arquillian, and also includes some some best practice to categorize the test case classes via Maven Profiles when you are using Maven.
Chapter 2: The Evolution of Testing is a review of the testing solution history for Java, especially for Java EE, and the pain and the lack of these legacy testing solution, and how Arquillian fills the blank table.
Chapter 3: Container Testing is a comprehensive reference of all popular Container supports. In this chapter, the popular embedded containers, managed containers, and remote containers will be introduced one by one. You can review this chapter frequently, when you are using Arquillian and some specific containers and encountering some problems in development .
Chapter 4: Why Did the Test Fail is a good beginning when you are a newbie of Arquillian, it will help find the reasons of the problems and resolve them gracefully when you are adopting Arquillian .
Chapter 5: Enriching the Enterprise Test Case , you will learn how to use Arquillian to test CDI and EJB in your enterprise application. It also provides some content for Spring application test with Arquillian.
Chapter 6: Arquillian Extensions extends what you have learned in Chapter 5, and introduces the JPA, Transaction testing, and it is also an introduction of the code coverage.
Chapter 7: Functional Application Testing , in this chapter you will learn how to use Selenium with Arquillian together, and use the Warp and Graphere arquillian extension to test modern Ajax and rich web application.
Chapter 8: Service Testing includes the approaches to test SOAP based web service and REST web service, also includes an introduction of JMS and Seam 2 testing.
Chapter 9: Arquillian and OSGI will introduce how to use Arquillian to test the OSGI bundle in JBoss and Glassfish application server.
Chapter 10: ShrinkWrap in Action is an excellent tutorial of the ShrinkWrap API, you can learn how to resolve the dependencies and package the test archive in detail.
You can review the detailed content table from the Arquillian Testing Guide book page of packt publishing website.
Thank the JBoss Arquillian Team for bringing the Arquillian to the Java world and a special thank to Johon D. Ament who wrote such a good book to all Arquillian fans. And thank Packt publishing for providing me excellent experience to review this book.
Enjoy reading!
标签：

评论

发表评论

此博客中的热门博文

AngularJS CakePHP Sample codes

Introduction This sample is a Blog application which has the same features with the official CakePHP Blog tutorial, the difference is AngularJS was used as frontend solution, and CakePHP was only use for building backend RESR API. Technologies AngularJS   is a popular JS framework in these days, brought by Google. In this example application, AngularJS and Bootstrap are used to implement the frontend pages. CakePHP   is one of the most popular PHP frameworks in the world. CakePHP is used as the backend REST API producer. MySQL   is used as the database in this sample application. A PHP runtime environment is also required, I was using   WAMP   under Windows system. Post links I assume you have some experience of PHP and CakePHP before, and know well about Apache server. Else you could read the official PHP introduction( php.net ) and browse the official CakePHP Blog tutorial to have basic knowledge about CakePHP. In these posts, I tried to follow the steps describ
2 条评论
阅读全文

JPA 2.1: Attribute Converter

JPA 2.1: Attribute Converter If you are using Hibernate, and want a customized type is supported in your Entity class, you could have to write a custom Hibernate Type. JPA 2.1 brings a new feature named attribute converter, which can help you convert your custom class type to JPA supported type. Create an Entity Reuse the   Post   entity class as example. @Entity @Table(name="POSTS") public class Post implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name="ID") private Long id; @Column(name="TITLE") private String title; @Column(name="BODY") private String body; @Temporal(javax.persistence.TemporalType.DATE) @Column(name="CREATED") private Date created; @Column(name="TAGS") private List<String> tags=new ArrayList<>(); } Create an attribute convert
发表评论
阅读全文

Auditing with Hibernate Envers

Auditing with Hibernate Envers The approaches provided in JPA lifecyle hook and Spring Data auditing only track the creation and last modification info of an Entity, but all the modification history are not tracked. Hibernate Envers fills the blank table. Since Hibernate 3.5, Envers is part of Hibernate core project. Configuration Configure Hibernate Envers in your project is very simple, just need to add   hibernate-envers   as project dependency. <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-envers</artifactId> </dependency> Done. No need extra Event listeners configuration as the early version. Basic Usage Hibernate Envers provides a simple   @Audited   annotation, you can place it on an Entity class or property of an Entity. @Audited private String description; If   @Audited   annotation is placed on a property, this property can be tracked. @Entity @Audited public class Signup implements Serializa
发表评论
阅读全文