Introduction to Arquillian framework

This Document, constitutes and contains proprietary information of ExcelaCom Technologies and shall not be disclosed in whole or in part by Client to any third party or to any employees of Client other than those who have a need to know such information, and shall not be duplicated or used by Client for any other purpose than to evaluate this Document.

Getting started with Arquillian Framework


The progression of a J2EE application testing

What is Arquillian ?

Why Arquillian ?

How to run Arquillian test ?

Shrink and Wrap

Demo

Arquillian Extensions

Agenda


The progression of a J2EE application testing

What is happening ?

• Unit testing

• Functional testing

• Integration Testing

• Performance Testing


- Does these actions adapt Agile or extreme programming methodologies ?

- Still Integration testing is painful.

- Run time configuration

- Run time management

- Running the Tests

What is needed for the current ?


Unit vs Integration testing :


The progression of a J2EE application testing…


What is Arquillian ?

- is a container-oriented testing framework that enablesdevelopers to create portable integration tests for enterpriseapplications;

- is a JBoss Community project.

The Arquillian framework is broken up into three major sections:

Test runners (JUnit or TestNG),

Containers (Weld, OpenWebBeans, Tomcat, Glassfish, and so on),

Test enrichers (integration of your test case into the container that

your code is running in).


Arquillian Architecture


- is a fluent API for creating archives such as JARs, WARs and EARs in Java;

- is also a JBoss Community project.


What is Test Runners ?


1. A remote container resides in a separate JVM from the test runner; Arquillian binds to the container to deploy and un deploy the test archive and invokes tests via a remote protocol(typically HTTP).

2. An embedded container resides in the same JVM as the test runner; lifecycle managed by Arquillian; tests are executed via a local protocol for containers without a web component (e.g., Embedded EJB) and via a remote protocol for containers that have a web component (e.g., Embedded Java EE).

3. A managed container is the same as a remote container, but in addition, its lifecycle (startup/shutdown) is managed by Arquillian and is run as a separate process

Container :


Example J2EE component :


Example Unit Test class :


Arquillian Test class :


Run it :


What is happening ?

- The CDI Bean Manager is used to create a new bean instance.

- Arquillian injects the bean into the test class instance, before running any tests


Who care about run time ?

Here comes Arquillian.

Just add dependency in Maven,

Rest of the things actually taken care by the framework,- starting the container run time- packaging the stuffs - deploying into the container - un deploying the package

- Stopping the containers run time.


Test Enrichers:

@Resource: It defines references to any JNDI entry as per standard naming and injection schemes.

@EJB: As long as you are including a deployed EJB in your archive, you can refer to it as long as your target container includes EJB support. EJB JNDI entry conventions remain intact. It is also worthwhile to note that Local and Remote interfaces matter. When you deploy to a same JVM application server, or a remote application server you must ensure that your injected test cases can see the EJB reference appropriately.

@Inject: This is available as long as you have deployed a valid bean archive (requires beans.xml in META-INF or WEB-INF).

And few more by extensions….


Let’s Demonstrate it :


So finally..


What else can be automated ?

-Write meaning full tests with endless options.

- Arquillian extensions.- Drone- Graphene- Warp- Persistence- Performance- Seam 2


Pro’s and Con’s

-Con’s- Maven hell

- one test class per @Deployment- too much capabilities – bit large learning curve

-Pro’s- Handy even for testers

- Portable- flexible - open source


Miscellaneous :


Reach Me:

- Karthikeyan Annamalai [email protected]

Introduction to Arquillian framework

Technology

Transcript of Introduction to Arquillian framework