See also http://statelessprime.blogspot.co.at/2015/04/extending-arquillian-graphene.html With Arquillian Graphene, you can write tests which inspect the GUI of your web application (HTML based ones) right from within your familiar Unit Test code structure. And there are already many nice features available, but sometimes, you want to extend the concepts of Arquillian Graphene. So that you can write cleaner code in some use cases. The good thing is that you can achieve this quite easily due to the internal structure of the framework which uses 'Enricher's and Service extensions.

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