Arquillian Graphene 2.0 - Functional Testing with ElegancePosted by +Lukáš Fryč
It’s already been a year since we announced the first alpha release of Graphene 2. Back then the Selenium project had undergone huge changes adopting the WebDriver API. We were excited to explore the new waters to make sure web applications are as easy to test as writing simple unit tests.
We quickly established some objectives for the project which evolved to what we can call Graphene 2.0 today:
* built on top of WebDriver,
* encourage to use/create reusable test abstractions,
* simplify testing of AJAX pages.
* fast development turnaround,
and last but not the least, we wanted to make sure people could use the same features that were part of Graphene 1. Now, one and half year after the Graphene 1.0.0.Final release, we can finally report that we were able to rope in all of the concepts anticipated back then. During this journey we’ve basically touched all APIs and adopted all of the features while leveraging the modern WebDriver API for browser automation.
Graphene now consists of more than 700 commits
from 11 code contributors
– and that fact leads me to another aspect:
We would like to thank everyone who have been involved with the project so far; early adopters, issue reporters, people who improved documentation and of course people who picked up a ball and contributed the code. You all hardened the project to the shape it is now.Thank you, you guys rock!
Sounds interesting? If you would like to know more about;
* How Graphene compares to WebDriver?
* What’s so cool about Graphene?
** Best Practices: Page Abstractions
** Testing AJAX
** Dependency Injection
* Learning Graphene
* Support and Compatibility Notes
* Release Details
Please read the full Graphene 2.0.0.Final Release Notes:http://arquillian.org/blog/2013/10/22/arquillian-graphene-2-0-0-Final/