The document presents Rudy De Busscher discussing the extension of Arquillian Graphene for testing Java applications. It focuses on the importance of integration testing, differentiating between unit and integration tests, and emphasizes the need for visual and client-side testing. The presentation includes discussions on using Arquillian with tools like Selenium WebDriver and Arquillian Drone for more efficient browser control during tests.

1. Extending Arquillian Graphene
Rudy De Busscher

2. Who Am I
Rudy De Busscher
C4J: Senior Java Web Developer, Java Coach
JSR375: Java EE Security API Expert group member
Java EE believer
@rdebusscher
http://jsfcorner.blogspot.be
http://javaeesquad.blogspot.be

3. Agenda
Testing
Integration
Testing
Arquillian
Extending
Graphene
DEMO

4. Testing
• As important as coding
• Developer testing
• Unit vs integration
• Visual?

5. GUI testing
• Integration
• Difficult
– All tiers involved
– Capture GUI state

6. Arquillian
• Motto:
– Test the real thing
1. In container testing
– Skip the build
2. Client side testing
– Test any Browser/HTML based UI

7. High level

8. • Integration
• Browser <-> database.
• In place / Testing the real thing
• Replace Human acceptance testing?
• Client side only (Graphene) or deep testing
(ex Warp for JSF)
Visual testing

9. Arquillian Graphene
Selenium Webdriver
• De facto standard
• Control browser from unit test
Arquillian Drone
• Wrapper around Selenium Webdriver
• Easier configuration

10. Demos

11. Q&A