12
Extending Arquillian Graphene Rudy De Busscher

Extending Arquillian graphene

Embed Size (px)

Citation preview

Page 1: Extending Arquillian graphene

Extending Arquillian Graphene

Rudy De Busscher

Page 2: Extending Arquillian graphene

Who Am I

Rudy De Busscher

C4J: Senior Java Web Developer, Java CoachJSR375: Java EE Security API Expert group member

Java EE believer

@rdebusscher

http://jsfcorner.blogspot.behttp://javaeesquad.blogspot.be

Page 3: Extending Arquillian graphene

AgendaTesting

Integration

Testing

Arquillian

Extending

Graphene

DEMO

Page 4: Extending Arquillian graphene

Testing

• As important as coding

• Developer testing

• Unit vs integration

• Visual?

Page 5: Extending Arquillian graphene

GUI testing

• Integration

• Difficult

– All tiers involved

– Capture GUI state

Page 6: Extending Arquillian graphene

Arquillian

• Motto:

– Test the real thing

1. In container testing

– Skip the build

2. Client side testing

– Test any Browser/HTML based UI

Page 7: Extending Arquillian graphene

High level

Page 8: Extending Arquillian graphene

• 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

Page 9: Extending Arquillian graphene

Arquillian Graphene

Selenium Webdriver

• De facto standard

• Control browser from unit test

Arquillian Drone

• Wrapper around Selenium Webdriver

• Easier configuration

Page 10: Extending Arquillian graphene

Demos

Page 11: Extending Arquillian graphene

Q&A

Page 12: Extending Arquillian graphene